Anyone using PostgreSQL with 10k concurrent connections, most of them idle? Let's say PgBouncer is not an option. Experiences? Asking for a friend ;)
-
-
Which is bad, because that's a very frequent task for a lot of workloads that use a lot of transaction - at the very least once a transaction (repeatable read), but more commonly at least two to three times (read committed).
-
You can quite easily see throughput drop w/ lots of active connections. And it gets a lot worse with bigger systems, as inter-socket traffic leads to significantly worse scalability behaviour.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.