3 ms·

> 2. Use a connection pooler ... I had my jaw dropped on that point -- they didn't use connection pooling? WTF? I'm seeing connection pools on pretty much any

> 2. Use a connection pooler ... I had my jaw dropped on that point -- they didn't use connection pooling? WTF? I'm seeing connection pools on pretty much any project I've worked on, even under 1/req/day load, it's pretty much "must have" since 90s. And it's really just a library (like dbcp2) and a few lines of config, with almost no drawbacks. I cannot believe engineers at GitLab level are so bad at, well, engineering. I'm losing faith in their produce, please show me that I'm wrong.

maccard 9y ago
Why are they bad at engineering just for not using a feature that you were aware of? If anything gitlab have proven to be reasonably good at engineering, given they’ve made it this far with a single postgre instance with no tweaking. It also speaks wonders for pg itself.
YorickPeterse 9y ago
We've had connection pooling on the client side since forever, just like any other Rails project. This article specifically talks about server side pooling.