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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

PostgreSQL benchmarks under giant lock free DragonflyBSD

61 点作者 unix-junkie超过 13 年前

2 条评论

JoachimSchipper大约 13 年前
Summary/background: DragonflyBSD split from FreeBSD (partly) over multicore strategy, FreeBSD going with threads and fine-grained kernel locks and DragonflyBSD going with a microkernel and multiple processes (not entirely dissimilar to GNU Hurd.)<p>This post shows a standard PostgreSQL benchmark on a big machine (2 cpus * 6 cores/cpu * 2 hardware threads/core, 96GB RAM) and the news is that Dragonfly is approaching FreeBSD's performance (while hopefully being more flexible/secure due to the microkernel design).<p>As an aside, Scientific Linux handily destroys both FreeBSD and DragonflyBSD in localhost benchmarks, but crashes rather a lot. (This seems odd, but the focus is on the DragonflyBSD / FreeBSD comparison anyway.)
评论 #3620751 未加载
评论 #3620691 未加载
评论 #3621044 未加载
评论 #3620776 未加载
foobarbazetc大约 13 年前
When you're "crashing" Scientific Linux (which I presume using a non-modified RHEL 6 kernel) then you're doing something wrong.<p>We run far bigger PostgreSQL DBs than this, and we've <i>never</i> had a RHEL crash. Ever.<p>Maybe there's something wrong with the hardware?<p>Additionally, if fsync = on in this test, then you're mixing a file system test with a database test.
评论 #3623575 未加载