m Kristina, Those numbers sound amazing, but there are a lot of missing details ;-). 0. what was the concurrency level? 0. where there concurrent CRUD operations? (basically I expect things to behave quite differently when sets of READS are (almost completely) separated from sets of WRITES) 0. what was the average data size/op? You know such benchmarks can be "fabricated" and missing information tends to encourage that kind of thought. LikeLike Reply kristina says:  May 00, 0000 at 0:00 pm 0. I have no idea. 0. Yes. 0. I have no idea. I think people are taking this post a bit too seriously... I just thought it was a really cool demo of what Mongo's going to be able to do: scale horizontally to practically infinite capacity. It's certainly not meant to be a benchmark. I think we're working on a more interesting application (one has actual functionality other than hammering the database) that we'll open source and use as a demo in the future. We'll also do some real benchmarks against sharding before releasing 0.0, obviously. LikeLike Reply kristina says:  May 00, 0000 at 0:00 am 0. I have no idea. 0. Yes. 0. I have no idea. I think people are taking this post a bit too seriously... I just thought it was a really cool demo of what Mongo's going to be able to do: scale horizontally to practically infinite capacity. It's certainly not meant to be a benchmark. I think we're working on a more interesting application (one has actual functionality other than hammering the database) that we'll open source and use as a demo in the future. We'll also do some real benchmarks against sharding before releasing 0.0, obviously. LikeLike Reply 