optimizing "random_page_cost" parameter
Today I red an article on Medium which claimed Postgres performance could be improved drasticially by optimizing the "random_page_cost" parameter for SSDs: https://medium.com/@rizqimulkisrc/the-hidden-postgresql-setting-that-doubled-query-speed-overnight-72803da1a13e
I saw that Neon did not use this optimization. Is there a reason?
Medium
The Hidden PostgreSQL Setting That Doubled Query Speed Overnight
One configuration change transformed a failing startup’s database from 8-second queries to 400ms responses
3 Replies
inland-turquoise•2mo ago
Hey! Forwarding to get an answer for you, thanks for sharing!
other-emerald•2mo ago
@Tristan Partin probably the best person here to answer that question, when he's online!
absent-sapphire•2mo ago
Accessing a random page on Neon can be costly because we have to hit the pageserver/object storage to fetch it. Neon has a local file cache on the computes to mitigate this