5 ms·

MongoDB: 8m ops/s on 25 servers (320k per server)

53 points by dmytton 16y ago

oliverkofoed 16y ago
Videos from MongoSF: http://www.10gen.com/event_mongosf_10apr30 http://www.10gen.com/event_mongosf_10apr30
meghan 16y ago
Here is a link to the video from the sharding talk at MongoSF http://blip.tv/file/3597247 http://blip.tv/file/3597247
fizx 16y ago
What's an "operation" in this context? Reading a boolean value? Incrementing a counter? Loading a 100kb document?
- moe 16y ago
  That question is spot on. We knew already that mongo is quite fast, so why throw this useless figure into the room without any context?
- kchodorow 16y ago
  "operation" is updates+inserts+reads+deletes+database commands, in ~1:1:10:1:1 ratio (IIRC). I don't know what the exact operations were, it was supposed to simulate a real-life web app distribution of requests.
jrockway 16y ago
WritingToAFileDB: 300M ops/s on my netbook with an SSD. (Where op == appending a byte.)
dmytton 16y ago
Although the numbers are not possible to read from the end of the video talk[1], it looks similar to the mongostat tool[2] (albeit a web version). If that is indeed the case, then the total operations will be the sum of all inserts, queries, updates, deletes, getmores and commands per second. Would need the 10gen guys to confirm though. [1] http://blip.tv/file/3597247 http://blip.tv/file/3597247 [2] http://www.mongodb.org/display/DOCS/mongostat http://www.mongodb.org/display/DOCS/mongostat
- kchodorow 16y ago
  Yes, exactly. The total was for all operations and, yeah, it's basically a GUI of mongostat.
- tlack 16y ago
  Wouldn't you say the nature of the benchmark is probably the most important detail, yet it is the one that is omitted from this blog post?
audidude 16y ago
were the ops sequential or random?
staunch 16y ago
That would be very impressive if it was a real world installation. That it's an entirely artificial benchmark makes it almost entirely meaningless. They should be bragging about the most impressive real world MongoDB setups, even if the numbers are smaller.
- mathias_10gen 16y ago
  This was at a talk on the state of mongodb's sharding features which are still a work in progress. The demo was a preview of what's to come rather than simple bragging.
jbellis 16y ago
320k per machine per second sounds really high, even granting high-end machines, since the non-10gen ops/s numbers I've seen have been in the 2k to 10k per second range (e.g., http://prajwal-tuladhar.net.np/2009/11/15/500/mongodbs-performance-as-compared-to-others-esp-couchdb/ http://prajwal-tuladhar.net.np/2009/11/15/500/mongodbs-perfo...).
- rit 16y ago
  To be fair - this benchmark is from 6 months ago. There have been a lot of improvements in Mongo since then. I also question his statement of "Slower than DB" - I have been in production w/ MongoDB since August '09 and it was a huge performance improvement over MySQL. Since then there have been incremental improvements in performance w/ each release.
rufo 16y ago
Not that I run a site that's anywhere close to Reddit, but I was a bit scared to hear one of their admins mention MongoDB "suffered more than one bout of catastrophic data loss in my brief testing": http://www.reddit.com/r/announcements/comments/c2spc/reddits_may_2010_state_of_the_servers_report_or/c0ptcaz http://www.reddit.com/r/announcements/comments/c2spc/reddits...
tszming 16y ago
i don't need 8m ops/s, but the single server durability http://jira.mongodb.org/browse/SERVER-980 http://jira.mongodb.org/browse/SERVER-980
ehwizard 16y ago
Some more info: - 25 x-large ec2 instances - each instance ran mongos, mongod and java loading program - system averaged 5M "ops" per second over many hours Average ops per server: - 3000 inserts - 25000 updates - 150000 queries - 1500 deletes - 50 getMore - 25000 command (getLastError)

53 points by dmytton 16y ago

oliverkofoed 16y ago

Videos from MongoSF: http://www.10gen.com/event_mongosf_10apr30 http://www.10gen.com/event_mongosf_10apr30

meghan 16y ago

Here is a link to the video from the sharding talk at MongoSF http://blip.tv/file/3597247 http://blip.tv/file/3597247

fizx 16y ago

What's an "operation" in this context? Reading a boolean value? Incrementing a counter? Loading a 100kb document?

moe 16y ago
That question is spot on. We knew already that mongo is quite fast, so why throw this useless figure into the room without any context?
kchodorow 16y ago
"operation" is updates+inserts+reads+deletes+database commands, in ~1:1:10:1:1 ratio (IIRC). I don't know what the exact operations were, it was supposed to simulate a real-life web app distribution of requests.

jrockway 16y ago

WritingToAFileDB: 300M ops/s on my netbook with an SSD. (Where op == appending a byte.)

dmytton 16y ago

Although the numbers are not possible to read from the end of the video talk[1], it looks similar to the mongostat tool[2] (albeit a web version). If that is indeed the case, then the total operations will be the sum of all inserts, queries, updates, deletes, getmores and commands per second. Would need the 10gen guys to confirm though. [1] http://blip.tv/file/3597247 http://blip.tv/file/3597247 [2] http://www.mongodb.org/display/DOCS/mongostat http://www.mongodb.org/display/DOCS/mongostat

kchodorow 16y ago
Yes, exactly. The total was for all operations and, yeah, it's basically a GUI of mongostat.
tlack 16y ago
Wouldn't you say the nature of the benchmark is probably the most important detail, yet it is the one that is omitted from this blog post?

audidude 16y ago

were the ops sequential or random?

staunch 16y ago

That would be very impressive if it was a real world installation. That it's an entirely artificial benchmark makes it almost entirely meaningless. They should be bragging about the most impressive real world MongoDB setups, even if the numbers are smaller.

mathias_10gen 16y ago
This was at a talk on the state of mongodb's sharding features which are still a work in progress. The demo was a preview of what's to come rather than simple bragging.

jbellis 16y ago

320k per machine per second sounds really high, even granting high-end machines, since the non-10gen ops/s numbers I've seen have been in the 2k to 10k per second range (e.g., http://prajwal-tuladhar.net.np/2009/11/15/500/mongodbs-performance-as-compared-to-others-esp-couchdb/ http://prajwal-tuladhar.net.np/2009/11/15/500/mongodbs-perfo...).

rit 16y ago
To be fair - this benchmark is from 6 months ago. There have been a lot of improvements in Mongo since then. I also question his statement of "Slower than DB" - I have been in production w/ MongoDB since August '09 and it was a huge performance improvement over MySQL. Since then there have been incremental improvements in performance w/ each release.

rufo 16y ago

Not that I run a site that's anywhere close to Reddit, but I was a bit scared to hear one of their admins mention MongoDB "suffered more than one bout of catastrophic data loss in my brief testing": http://www.reddit.com/r/announcements/comments/c2spc/reddits_may_2010_state_of_the_servers_report_or/c0ptcaz http://www.reddit.com/r/announcements/comments/c2spc/reddits...

tszming 16y ago

i don't need 8m ops/s, but the single server durability http://jira.mongodb.org/browse/SERVER-980 http://jira.mongodb.org/browse/SERVER-980

ehwizard 16y ago

Some more info: - 25 x-large ec2 instances - each instance ran mongos, mongod and java loading program - system averaged 5M "ops" per second over many hours Average ops per server: - 3000 inserts - 25000 updates - 150000 queries - 1500 deletes - 50 getMore - 25000 command (getLastError)