3 ms·

MongoDB VERY CLEARLY warns you about the limitations of the 32-bit install when you spin it up. When I invoke mongod on my 32-bit development box, I get a nice

by cheald 16y ago

MongoDB VERY CLEARLY warns you about the limitations of the 32-bit install when you spin it up. When I invoke mongod on my 32-bit development box, I get a nice big message: ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data ** see http://blog.mongodb.org/post/137788967/32-bit-limitations for more If you manage to miss that, it's your own fault. Combined with the fact that he was using an unstable development branch, he has absolutely zero room whatsoever to complain. He hit a documented limit and got less-than-friendly behavior on an unstable build of the software. Going nuclear over it is just silly, and makes him look inattentive and/or naive.

bad_user 16y ago
That seems like a brutal limitation done for non-obvious reasons ... I mean, wtf? > makes him look inattentive and/or naive Oh I wish you gave me more options. This is not a proper ad hominem.
- cheald 16y ago
  It's a brutal limitation if you're expecting MongoDB to be "MySQL, except with more awesome because it's new and shiny!", sure, but once you read the blog post, it's quite apparent why - memory-mapped files are blisteringly fast, and raw speed at the cost of other features (like relational constraints, transactions, and single-server durability) is a part of the MongoDB setup. If those are acceptable sacrifices, then great, enjoy a wicked fast data store. If they're not, then it's not the tool for you, no matter how much the cool kids chat it up.
grasshoper 16y ago
Spot on. I came here to say just this. Dev branch or not, there is no way he could have missed this. I don't know how you can better advertise a limitation than this. Maybe he didn't realize he was on a 32-bit box. Maybe he didn't pay attention to how much data he would be using. If you want to use Mongo for something serious, make sure you're on a 64-bit box. Memory-mapped file I/O is an important part of what makes Mongo so fast and attractive, but it has obvious limitations on a 32-bit box.

by cheald 16y ago

bad_user 16y ago

That seems like a brutal limitation done for non-obvious reasons ... I mean, wtf? > makes him look inattentive and/or naive Oh I wish you gave me more options. This is not a proper ad hominem.

cheald 16y ago
It's a brutal limitation if you're expecting MongoDB to be "MySQL, except with more awesome because it's new and shiny!", sure, but once you read the blog post, it's quite apparent why - memory-mapped files are blisteringly fast, and raw speed at the cost of other features (like relational constraints, transactions, and single-server durability) is a part of the MongoDB setup. If those are acceptable sacrifices, then great, enjoy a wicked fast data store. If they're not, then it's not the tool for you, no matter how much the cool kids chat it up.

grasshoper 16y ago

Spot on. I came here to say just this. Dev branch or not, there is no way he could have missed this. I don't know how you can better advertise a limitation than this. Maybe he didn't realize he was on a 32-bit box. Maybe he didn't pay attention to how much data he would be using. If you want to use Mongo for something serious, make sure you're on a 64-bit box. Memory-mapped file I/O is an important part of what makes Mongo so fast and attractive, but it has obvious limitations on a 32-bit box.