MONGODB3.0 Performance Test Report II

mongodb3.0 Performance Test Report One

MONGODB3.0 Performance Test Report II

MONGODB3.0 Performance Test Report three

Test environment:

Server: X86 pcserver total 6 units

CPU: Single 8-core

Memory: 64G

Disk: RAID 10

Operating system: CentOS 6.5

mongodb:3.0

Java Driver: 2.13.0

jdk:1.6

Network: Gigabit Ethernet

Test scenario:

single Monodb service, one with configuration server as the pressure server, the amount of data does not exceed the memory size.

The background in the library is 100 million data of size 10K.

The query is randomly inserted at the ID, inserting 10k of data at a time.

10 thread Insert, 10 thread query.

Before testing. A large number of random queries are performed until the memory does not grow

Here is the MongoDB 3.0 test Result:

Insertion speed average 9229 per second

Query speed average 2102 per second

Here is the MongoDB 2.0 test Result:

Insertion speed Average 169 per second

Query speed average 254 per second

Analysis: 1. Limited by the network, the corresponding 10k data, insert or query theory the maximum speed should be 12500. The 3.0 version of the insertion efficiency should be the largest embodiment.

2. In mixed mode, 2.4.4 version number performance is too poor, it appears that the 3.0 version of the document-level lock performance is greatly improved.

3. Insert and query for 2.4.4 Test 10 thread case, insert in 9,000 times/second or so, query in 800 times/second, look at the library level of the lock on the mixed mode is still very large.

4.3.0 in the case of a single 10 thread, the query is 1900 times/second, and the Btree index improves query performance by one time.

5. The same amount of data, 3.0 version number than the 2.4.4 version number, memory nearly add one times. It appears to be space-changing performance.

For 3.0. The insertion has reached the network limit, but the query does not, increase the query to 20 threads, that is, 10 thread inserts, 20 thread queries.

Insertion speed average 4622 insertion speed is unstable

Query speed average 2530 per second

It seems that a large number of queries can affect the insertion speed, causing the insertion to be very unstable. Create a replica set. It is a good choice to distribute the query to the replica.

Finally, the Shard performance test is performed.

MONGODB3.0 Performance Test Report II