4 ms·
Very sparse on details. Are they partitioning the data? If so how? Is it MongoDB shards or at the application level or...? What's their average record size? Do
by pierrefar 16y ago
Very sparse on details. Are they partitioning the data? If so how? Is it MongoDB shards or at the application level or...? What's their average record size? Do they see a long-tail kind of access such that MongoDB really does keep the most commonly used records in memory all the time? How many machines are they serving from? What are their specs (particularly RAM)?
- kneath 16y agoThis is pretty well covered in this presentation: http://www.slideshare.net/fehguy/migrating-from-mysql-to-mongodb-at-wordnik http://www.slideshare.net/fehguy/migrating-from-mysql-to-mon... A few unanswered questions (sharding? Looks like none to me), but a good bit of numbers and specifics on their current setup.
- ericflo 16y agoThe 47.7 queries per second figure in those slides surprised me a bit. I'd like to know more details there...is that for a single node, or the entire cluster?
- fehguy 16y agoThat's per api server, we have 4 api servers.
- meghan 16y agoVideo of this talk is available here: http://blip.tv/file/3621377 http://blip.tv/file/3621377 This article also has some details: http://www.royans.net/arch/mongodb-migration-from-mysql-at-wordnik/ http://www.royans.net/arch/mongodb-migration-from-mysql-at-w...
- deleted 16y ago[deleted]
- johnny99 16y agoSome of these questions are answered in a separate set of slides, which the author links to in the comments of the post. Hardware looks like a single server, 2x4 core CPUs, 32 GB of RAM, and a FC SAN.
- ericflo 16y agoSingle node, eh? I thought MongoDB was not supposed to be run in that configuration.
- thegoleffect 16y agoThey're probably running 1+ Mongod process/node per core - not exactly ideal though.
- fehguy 16y agoWe run one mongod master, one slave (soon to be two slaves). These are used across all the api servers.