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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

GitLab is down. Again.

6 点作者 openbasic大约 7 年前

2 条评论

foobarbazetc大约 7 年前
A bunch of thoughts from a guy running postgres on a large site:<p>A restore rate of 100Gb&#x2F;hour is way too low.<p>Over a 10GigE interface with a semi-decent SSD RAID you should be pushing 1Gb&#x2F;second <i>easily</i>.<p>Also, pgbouncer is never the problem. If it’s complaining it’s either configured wrong or the database is having a bad time.<p>I’d be scared out of my mind if this was my service and I was running it all on a single master with no usable backups. Then making it worse by letting production traffic hit it thereby moving the database further and further from when the isssue occurred.<p>Those snapshots are going to be unusable unlsss the underlying FS is frozen before the snapshot gets taken.<p>Honestly reading the notes (and not knowing anything about the team) they need less DevOps and more SysAdmin&#x2F;DBA.
评论 #16932584 未加载
reacharavindh大约 7 年前
Serious question: Would it be better if we had services that did not &quot;move fast and break things&quot;? particularly when dealing with user facing components like this?<p>Imagine a gitlab product that goes into operation, and gets updated with a good load of features every 3 or 6 months? The ones they replace with is thoroughly tested internally?
评论 #16933058 未加载