TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Analyzing the Limits of Connection Scalability in Postgres

112 点作者 ozgune超过 4 年前

4 条评论

jeff-davis超过 4 年前
The linked post is slightly outdated. Related discussion on a subsequent post:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=24887676" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=24887676</a>
评论 #25036755 未加载
1996超过 4 年前
Great article that matches my experiences: running with max_connections=100000 is not an issue when you have more than enough ram, the problem is the idle connections that you are tempted to tolerate (after all, you&#x27;ve got lots of RAM, so why bother?) linearly decrease the TPS even if nothing is done<p>pgbouncer does help, but brings in unneeded complexity.<p>postgres 14 should offer an &quot;alternate&quot; port doing essentially what pgbouncer does, next to the regular port.<p>Typical usecase: a large fleet of IOT devices with a write-only access to a central database, feeding new data every second. No visibility of the current transactions is needed.
评论 #25040520 未加载
评论 #25039224 未加载
anarazel超过 4 年前
Author here, happy to answer questions &amp; criticism.
评论 #25038414 未加载
TedShiller超过 4 年前
Funny that Microsoft of all companies is talking about limits in other software
评论 #25042258 未加载