M
MongoDB Engineering Blog
engineering.mongodb.com · Company blog · on HN since 2016
MongoDB's engineering team writes about database internals, storage engines, build tooling, CI systems and developer workflow at the company.
What HN saysHN commenters link it for the story of switching from SpiderMonkey to V8 and back, and for the post explaining why MongoDB built its own CI system instead of using Jenkins.
17HN people shared it
3linked it in comments
29stories submitted
425story points
5 years agolast shared
2016people per year2026
Most-shared posts
- 1Getting storage engines ready for fast storage devices3 people · 4 points · first shared 2020 · discussion on HN
- 2We Replaced an SSD with Storage Class Memory2 people · 138 points · first shared 2020 · 68 comments on HN
- 3Transpiling between any programming languages (2019)2 people · 73 points · first shared 2019 · 50 comments on HN
- 4Succeeding with ClangFormat2 people · 11 points · first shared 2016 · discussion on HN
- 5A MongoDB Engineering Response to the Anti-Diversity-Effort Manifesto2 people · 7 points · first shared 2017 · discussion on HN
- 6Pruning Dynamic Rebuilds with libabigail2 people · 5 points · first shared 2018 · 1 comments on HN
- 7Considering the Community Effects of Introducing an Official MongoDB Go Driver2 people · 4 points · first shared 2018 · discussion on HN
- 8Causal guarantees are anything but casual2 people · 4 points · first shared 2018 · discussion on HN
- 9Code-generating away the boilerplate in our migration back to SpiderMonkey2 people · 4 points · first shared 2016 · discussion on HN
- 10Digging into D3 Internals to Eliminate Jank Over Large Data Sets2 people · 3 points · first shared 2016 · discussion on HN
- 11Farewell, Solaris1 people · 113 points · first shared 2017 · 53 comments on HN
- 12Testing Linearizability with Jepsen and Evergreen: “Call Me Continuously”1 people · 28 points · first shared 2017 · 4 comments on HN
- 13MongoDB’s JavaScript Fuzzer: Creating Chaos1 people · 13 points · first shared 2016 · discussion on HN
- 14Breaking the WiredTiger Logjam: The Write-Ahead Log1 people · 8 points · first shared 2017 · discussion on HN
- 15Repeatable performance tests: CPU options are best disabled1 people · 4 points · first shared 2019 · discussion on HN
What HN people wrote when they linked it
jiripospisil · 2022-01-12
Interestingly, MongoDB switched from SpiderMonkey to V8 only to switch back a few releases later.
https://engineering.mongodb.com/post/code-generating-away-the-boilerpl…
throwdbaaway · 2021-05-21
Well, I'll be the first one to admit that I was naive to expect <5% variance prior to this experience. But I guess you are going to far by framing this as a common wisdom?
In the HN discussion about cockroachdb cloud report 2021 (https://news.ycombinator.com/item?id=25811532), there was only 1 comment thread that talks about "cloud weather".
In https://engineering.mongodb.com/post/reducing-variability-in-performan… high profile engineers still claimed that it is perfectly fine to use cloud for performance testing, and "EC2 instances are neither good nor bad".
Of course, both the cockroachdb and mongodb cases could be related, as any performance variance at the instance level could be masked when the instances form a cluster, and the workload can be served by any node within the cluster.
metheus · 2017-02-07
> Is there a comparison to Jenkins available?
Not exactly, but we published a blog post about why we took the time to write a new CI system, and that post does touch upon why we didn't use Jenkins + plugins.
https://engineering.mongodb.com/post/evergreen-continuous-integration-…