MongoDB 3.2 WiredTiger storage engine performance test

MongoDB 3.2 WiredTiger storage engine performance test

MongoDB 3.2 was recently released. It uses WiredTiger as its default storage engine. Over the past five years, MongoDB has developed rapidly from its birth to its popularity.

MongoDB 3.0 began to support the "pluggable storage engine" function, so it is reasonable to use WiredTiger in version 3.2. The WiredTiger engine is based on the B-Tree algorithm. B-tree is a multi-path search Tree, non-binary tree. It is a common data structure, using the B-tree structure can significantly reduce the intermediate process experienced when locating records, thus accelerating access. B is short for Balance. The B-Tree data structure is generally used for database indexing, with a high overall efficiency.

The performance of the WiredTiger engine based on the B-Tree algorithm is superior to that of RocksDB and PerconaFT optimized for I/O. However, the WiredTiger 3.0 Engine has the problem of IO performance attenuation. It is reported that the performance of the WiredTiger 3.2 engine has been greatly improved on the basis of the 3.0 version. Let's take a look at the Benchmark Test of the WiredTiger 3.2 engine. Testing not only focuses on its performance, but also on the execution of checkpoints.

Test using the iiBench tool, which can be found at: https://github.com/mdcallag/iibench-mongodb

Iibench-mongodb tool usage requirements:

• Java 1.6 or 1.7
• The Java driver of MongoDB must be included in the class path.

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 Status:

• Storage Device: Intel ssd dc P3600 SSD 1.6 TB
• Host CPU: Bare Metal powered by Intel (R) Xeon (R) CPU E5-2680
• Test Dataset: 0.2 billion records, one index

Test results:

The WiredTiger 3.2 engine is indeed faster. It took 31 minutes for the WiredTiger 3.2 engine to complete the execution, and 51 minutes for the WiredTiger 3.0 Engine.

However, the WiredTiger 3.2 engine still has some problems. During the test, WiredTiger refused to process data in about one minute.

For more MongoDB tutorials, see the following:

CentOS compilation and installation of php extensions for MongoDB and mongoDB

CentOS 6 install MongoDB and server configuration using yum

Install MongoDB2.4.3 in Ubuntu 13.04

MongoDB beginners must read (both concepts and practices)

MongoDB Installation Guide for Ubunu 14.04

MongoDB authoritative Guide (The Definitive Guide) in English [PDF]

Nagios monitoring MongoDB sharded cluster service practice

Build MongoDB Service Based on CentOS 6.5 Operating System

MongoDB details: click here
MongoDB: click here

This article permanently updates the link address: