I'm not sure if they are still doing it, but they used to work on the highest voted stuff as a priority; so if you want a feature, vote.
Also, I'm working on Snappy compression with Mongo (it's already used for the journal), however it's not currently stable and work is sporadic due to my startup.
Re:MongoDB Gotchas and How To Avoid Them
by codewright on Monday November 05, 2012 @04:36PM
(#4745927)
It's probably not a clear win in most use-cases.
Re:MongoDB Gotchas and How To Avoid Them
by rogerbinns on Tuesday November 06, 2012 @03:14AM
(#4747625)
Reducing the working set is a big win. Mongo's behaviour when the working set is larger than RAM is really bad- https://jira.mongodb.org/browse/SERVER-574
Compression could have drawbacks on documents that get updated frequently. But it will be extremely useful on documents that get created and rarely/never change, coincidentally what I mostly have.
It would also greatly help if keys are compressed or indexed in some way since it could be done transparently.
You may recall the Mongo team being reluctant to make the database function well in single server setups, but they did address that with journalling.
The Mongo team seem somewhat reluctant to implement it.