MongoDB version 3.2 Wiredtiger Storage Engine performance test

MongoDB version 3.2 Wiredtiger storage engine performance test Chszs, not allowed to reprint without Bo master. Permission to reprint should be marked by the author and blog home: Http://blog.csdn.net/chszs

MongoDB 3.2 was recently released, and it uses Wiredtiger as its default storage engine. Over the past five years, MongoDB has evolved from birth to popularity, and it has grown quite rapidly.

MongoDB 3.0 began to support the "Pluggable Storage Engine" feature, so the use of Wiredtiger in version 3.2 was also understandable. Wiredtiger engine based on B-tree algorithm, B-tree is a multi-path search tree, non-binary tree, is a common data structure, the use of b-tree structure can significantly reduce the location of records experienced in the intermediate process, thereby speeding up access speed. B is the abbreviation of balance, the B-tree data structure is generally used for database index, the comprehensive efficiency is high.

The Wiredtiger engine based on the B-tree algorithm should perform better than Rocksdb and perconaft for IO optimizations, but the Wiredtiger 3.0 engine has an IO performance attenuation problem. It is reported that the performance of the Wiredtiger 3.2 engine in the 3.0 version of the basis of a larger upgrade, the following can see the Wiredtiger 3.2 engine benchmark. The test not only pays attention to its performance, but also focuses on the execution of the checkpoint.

Test using the Iibench tool, this tool address: Https://github.com/mdcallag/iibench-mongodb

Iibench-mongodb Tool Usage Requirements:

• Java version 1.6 or 1.7
• The Java driver for MongoDB must be included in the Classpath

For example in Classpath:

# cd /home# wget http://central.maven.org/maven2/org/mongodb/mongo-java-driver/3.2.0/mongo-java-driver-3.2.0.jar# export CLASSPATH=/home/mongo-java-driver-3.2.0.jar:$CLASSPATH

Wiredtiger command line:

numactl --interleave=all ./mongod --dbpath=/mnt/i3600/mongo/ --storageEngine=wiredTiger --syncdelay=900 --wiredTigerCacheSizeGB=10 --wiredTigerJournalCompressor=none

Server condition:

• Storage device: Intel SSD DC P3600 SSD 1.6TB
• Host Cpu:bare Metal Powered by Intel (R) Xeon (r) CPU e5-2680
• Test data set: 200 million records, single index

Test results:

The Wiredtiger 3.2 engine is really faster. The completion of the Wiredtiger 3.2 engine took 31 minutes, while the Wiredtiger 3.0 engine took 51 minutes.

However, there are still some problems with the Wiredtiger 3.2 engine. During the test, Wiredtiger had a minute or so of time to refuse to process the data.

MongoDB version 3.2 Wiredtiger Storage Engine performance test