The discussion revolves around expected 99th percentile performance on a self-hosted high-volume site. pfaffman is concerned about performance issues despite the site owner believing the hardware is sufficient. Prometheus/Grafana metrics show 99th percentile response times reaching 2-3 seconds, with spikes up to 25 seconds, suggesting potential database bottlenecks. sam identifies Postgres as the likely culprit, noting that their hosted sites maintain sub-400ms 99th percentile performance. pfaffman plans to increase db_shared_buffers to 16GB and considers adjusting db_work_mem, noting the database is 30GB with 24GB of system RAM and concerns about slow disk performance. Despite the issues, the site owner is satisfied, and pfaffman decides to leave things as-is. trying2survive asks for configuration details on feeding container CPU and memory usage from Prometheus to Grafana.
I have migrated a high-volume site from Hosted to self-hosted for someone else to manage. I would like to provide them with as much information as possible to have them be successful in managing the site. This person is convinced that his hardware is more than sufficient to the task, but the page performance seems to suggest otherwise. I’m not sure whether there is more tuning that I should do or whether the hardware is to blame.
The database is 30GB on disk. There is reason to believe that the disk is slow. This is with db_work_mem=90MB and 10GB for db_shared_buffers. There is 24GB of system RAM. My next move is to bump db_shared_buffers to 16GB. Does that make sense? Should I bump db_work_mem too?
Today so far there have been spikes in the 5, 10, and 25 second ranges.
Edit: the site owner is happy with the performance. I remain interested in the answer to the question, but it looks like I’ll leave things as they are.
Hi. Did you get Prometheus to feed the container CPU and memory usage to Grafana already? If yes, would it be alright to tell the configuration? Thank you.