[SERVER-20176] Deletes with j:true slower on WT than MMAPv1 - MongoDB

XML

Word

Printable

j:true is expectedly slower than not, but WT is much slower than MMAPv1:

MMAPv1

> for(x=0;x<10000;x++){db.test.insert( { x : x } ) }

WriteResult({ "nInserted" : 1 })

> var start=new Date();db.test.remove( { } );duration=new Date() - start

> for(x=0;x<10000;x++){db.test.insert( { x : x } ) }

WriteResult({ "nInserted" : 1 })

> var start=new Date();db.test.remove( { }, { writeConcern : {j:true}} );duration=new Date() - start

> for(x=0;x<10000;x++){db.test.insert( { x : x } ) }

WriteResult({ "nInserted" : 1 })

> var start=new Date();db.test.remove( { } );duration=new Date() - start

> for(x=0;x<10000;x++){db.test.insert( { x : x } ) }

WriteResult({ "nInserted" : 1 })

> var start=new Date();db.test.remove( { }, { writeConcern : {j:true}} );duration=new Date() - start

depends on

WT-2104 add support for flushing the transaction log.

is duplicated by

SERVER-20576 Calling WiredTigerRecoveryUnit::waitUntilDurableWiredtiger without journaling returns an error

SERVER-18746 ensure WT write-ahead log flush is asynchronous from writes

related to

SERVER-20617 wt_nojournal_toggle.js failing intermittently in noPassthrough_WT

SERVER-17489 in bulk ops, only mark last operation with commit=synchronous