MongoDB 2.8.0-rc0 has been released and is ready for testing. This is the culmination of the 2.7.x development series.
2.8 Release Notes: http://docs.mongodb.org/
Downloads: http://www.mongodb.org/
We’re launching the second MongoDB Bug Hunt, a 3 week sprint in which the community will be rewarded for its efforts to find bugs and improve MongoDB. The MongoDB engineering team will be awarding prizes to people who find the most critical bugs. More details on the MongoDB Bug Hunt can be found at http://blog.mongodb.org/post/
Just checked the release notes about the availability of WiredTiger as a storage engine. Are there any benchmarks on using MMAPv1 vs WiredTiger in MongoDB? Any recommendations to use one over the other w.r.t a particular use case/scenario?
There aren't any benchmarks available at this time as far as I'm aware. I believe we will be releasing some examples comparing WiredTiger with MMAPv1 when 2.8 is released. The expectation is that WiredTiger will generally provide better performance for most use cases. It will be possible to have mixed storage engines within one replica set, so users will be able to add a new replica set member on a different storage engine and use it to experiment with an new storage engine before committing to a change.
Ok, thank you.
2.7.x was a development release series. 2.8.x is a stable release series.
2.9.x will be our next development series.
MongoDB has used this release numbering scheme for quite some time. It's the same odd/even pattern that Linux used until the 2.6 kernel
댓글 없음:
댓글 쓰기