5 ms·
I'm _really_ disappointed with the managed DB service. The "75 simultaneous connections per gigabyte of usable memory" limitation means cost wise it's cheaper j
by invisiblea 6y ago
I'm _really_ disappointed with the managed DB service. The "75 simultaneous connections per gigabyte of usable memory" limitation means cost wise it's cheaper just to spin up a 'real' database droplet.
- coder543 6y ago> means cost wise it's cheaper just to spin up a 'real' database droplet. This is the case for literally every managed database service that I'm aware of. You pay a premium for the managed aspect.
- invisiblea 6y agoThat's an entirely fair point, but frustrating that the connection limits are not clearer in the docs.
- coder543 6y agoFWIW, if you’re using 75+ connections, it’s probably a good idea to add some kind of Postgres proxy in the middle like pgbouncer. Postgres doesn’t handle lots of connections well because each connection forks off its own full OS process, and the performance can degrade noticeably when you have too many connections to Postgres as a result. That’s been my experience, at least.
- fastball 6y agoAnd DO's hosted Postgres allows you to easily configure pgbouncer.
- fastball 6y agoI'm very happy with the managed DB service. A few gotchas, but the service itself has been incredibly stable with 100% uptime from what I can tell.