MongoDB 1.4 Ready for Production

MongoDB
March 25, 2010 | Updated: January 20, 2017
#Releases

The MongoDB team is very excited to announce the release of MongoDB 1.4.0. This is the culmination of 3 months of work in the 1.3 branch and has a large number of very important changes.

Many users have been running 1.3 in production, so this release is already very thoroghly vetted both by our regressions systems and by real users.

Some highlights:

Core server enhancements

concurrency improvements
indexing memory improvements
background index creation
better detection of regular expressions so the index can be used in more cases
performance numbers

Replication & Sharding

better handling for restarting slaves offline for a while
fast new slaves from snapshots
configurable slave delay
replication handles clock skew on master
$inc replication fixes
sharding alpha 3 - notably 2 phase commit on config servers

Deployment & production

configure “slow” for profiling
ability to do fsync + lock for backing up raw files
option for separate directory per db
http://localhost:28017/_status to get serverStatus via http
REST interface is off by default for security (–rest to enable)
can rotate logs with a db command, logRotate
enhancements to serverStatus - counters/replication lag
new mongostat tool and db.serverStatus() enhancements

Query language improvements

$all with regex
$not
partial matching of array elements $elemMatch
$ operator for updating arrays
$addToSet
$unset
$pull supports object matching
$set with array indices

Geo

2d geospatial search
geo $center and $box searches

Downloads: www.mongodb.org/display/DOCS/Downloads

Full Change Log: jira

Release Notes: http://www.mongodb.org/display/DOCS/1.4+Release+Notes

Thanks for all your continued support, and we hope MongoDB 1.4 works great for you.

As always, please let us know of any issues,

-Eliot and the MongoDB Team

← Previous

MongoDB 1.4 Performance

We generally avoid posting benchmarks and suggest people create their own targeting their use cases. However, we have decided to publish a few of our internal micro-benchmarks comparing 1.2 with 1.4RC2 (aka 1.3.5) to show that in almost all cases performance is the same or better (sometime significantly so), even though we’ve added many new features. The test works by spawning N threads and having them hammer the DB with one operation as fast as they can. It is probably best to ignore the raw numbers and only look at the relative performance. In particular, these numbers shouldn’t be compared against other databases. Results Code for benchmarks A few highlights (and one lowlight): Single threaded query performance increased slightly Query performance increases linearly or super-linearly as more cores are used Insert performance increases by 10-30% vs 1.2 It is usually faster to create an index after importing your data than before. More so in 1.4. Not shown, but performance for both 1.2 and 1.4 held steady from 10 threads up to at least 500 threads. Even where it looks like the lines will cross, they do not. Update and Upsert performance is the same or higher until using more than 4 hammering threads. In practice, this shouldn’t effect users unless they are already doing more updates per second than the server can handle. Even so, we will look into solutions to this in the 1.5.x series. This test was run on an Intel Core i7 Quad 860 2.8GHz with 8GB of RAM and an Intel G2 SSD. Even though they improved performance, HyperThreading and TurboBoost were disabled as they can skew results in nondeterministic ways.

March 25, 2010

Next →

HalaPlay proves 1,500 percent growth is no fantasy, thanks to MongoDB Atlas and MongoDB Realm

Learn how MongoDB Realm's application development services helped Halaplay — a fantasy sports league — rapidly build new features and scale to 9 million users.

September 18, 2020