Tokumx VS mongodb read performance

I've been reading performance benchmarks comparing Tokumx and pure Mongodb.

• Tokumx Community Edition 2.0.0
• MongoDB 2.6.4_1

Both Tokumksa and Mongodba worked on the same machine.

Equipment overview:

Model Name: Mac mini
Model Identifier: Macmini6,1
Processor Name: Intel Core i5
Processor Speed: 2.5 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 10 GB

      

        
        
        
      

    

There is only one collection per instance. Each collection has 100,000 records.

For tokumx, it was created as a partitioned set. But for mongodb it was created like a normal collection:

db.createCollection("sample", {partitioned: true, primaryKey:  {field1:1, _id: 1}});

      

        
        
        
      

    

And for both instances, the index looks like this:

db.sample.ensureIndex({field1:1});
db.sample.ensureIndex({field2:1});
db.sample.ensureIndex({field3:1});
db.sample.ensureIndex({field4:1});
db.sample.ensureIndex({geo:"2d"});
db.sample.ensureIndex({"created_at":1});

      

        
        
        
      

    

I used Tsung to do stress testing. In terms of testing, I did a simple search, look field2

and geo

order of the fields by created_at

desc.

<clients>
<client host="localhost" use_controller_vm="false" maxusers="8000"/>
</clients>
<servers>
<server host="jchimac.thenetcircle.lab" port="8080" type="tcp"/>
</servers>
<load duration="5" unit="minute">
<arrivalphase phase="1" duration="5" unit="minute">
<users interarrival="0.03" unit="second"/>
</arrivalphase>
</load>

      

        
        
        
      

    

According to the official document, the transaction should be like TOKUMX ™ BENCHMARK VS. MONGODB - HDD

But in my testing:

TOKUMX:

MongoDB:

I am asking here to know if anyone can give any hint on this? Am I missing something in all testing?

Update:

I did another round of testing on Linux (CentOS):

CentOS release 6.5 (Final)
2.6.32-504.1.3.el6.x86_64 GNU/Linux
MemTotal:       24589896 kB
CPU: 12* (Intel(R) Xeon(R) CPU E5645  @ 2.40GHz)

      

        
        
        
      

    

Sample data looks like this:

{
  "_id": ObjectId("54867dc8ffbc15aa2bc3ee0e"),
  "_iid": 15,
  "_pid": 15,
  "uid": 102296,
  "nickname": "nickname_102296",
  "gender": 3,
  "image_id": 15,
  "created_at": 1418100168,
  "tag": 1,
  "geo": {
    "lat": 51.590449999999997033,
    "lon": 6.9671900000000004383
  }
}

      

        
        
        
      

    

Each collection contains 1,000,000 records.

Indexes in each collection (regular collections are created):

db.createCollection("coll", {primaryKey:  {_pid:1, _id: 1}});
db.tokumx_coll.ensureIndex({gender:1}); 
db.tokumx_coll.ensureIndex({uid:1}); 
db.tokumx_coll.ensureIndex({geo:"2d"}); 
db.tokumx_coll.ensureIndex({_pid:1}); 
db.tokumx_coll.ensureIndex({_iid:1}); 
db.tokumx_coll.ensureIndex({"created_at":1}); 

      

        
        
        
      

    

The test plan is also pretty simple:

{'$query', {gender,3,geo, {'$geoWithin', {'$center', [[48.72761, 9.24596], 0.005]}}}, '$orderby',{'_pid',-1}} 

      

        
        
        
      

    

Tsung Stress Test runs for 1 hour for each test. And the concurrency is 1 request per second.

  <load>
    <arrivalphase phase="1" duration="60" unit="minute">
      <users interarrival="1" unit="second"/>
    </arrivalphase>
  </load>

      

        
        
        
      

    

Here is the report in the screenshot:

TOKUMX:

MongoDB:

Updates @ 2014.12.12 Found: https://github.com/Tokutek/mongo/issues/1014