29 ms·
> Are you running an equivalent hardware setup? > there is no proof that PostgreSQL does not have any teething problems on high capacity hardware either At Dis
by bretthoerner 15y ago
> Are you running an equivalent hardware setup?
> there is no proof that PostgreSQL does not have any teething problems on high capacity hardware either
At Disqus we run Postgres on even larger boxes without pauses described here. We would have (had to) migrate off long ago if this were par for the course.
- gleb 15y agoThere is similar problem in Postgres as well. Not nearly as bad in magnitude, and with some shared responsibility with Linux and file system code (since PG relies of filesystem's caching). Greg Smith talked about it in some detail during PGWest 2010. One of his customers had long stalls in production and Greg worked out how to reproduce and explain them. He had some patches he was planning for Postgres 9.1, not sure if they went in.
- spudlyo 15y agoIs your database extremely write heavy? You don't usually see this problem in a more balanced read/write workload. Postgres has in the past suffered from stalls and lockups that can happen at checkpoint intervals, but it appears they mostly happen for seconds rather than minutes.