Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
3.0.6, 3.1.7
-
None
-
Fully Compatible
-
ALL
-
Quint 9 09/18/15
Description
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
|
70
|
> 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
|
94
|
WT
> 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
|
189
|
> 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
|
95113
|
Attachments
Issue Links
- depends on
-
WT-2104 add support for flushing the transaction log.
-
- Closed
-
- is duplicated by
-
SERVER-20576 Calling WiredTigerRecoveryUnit::waitUntilDurableWiredtiger without journaling returns an error
-
- Closed
-
-
SERVER-18746 ensure WT write-ahead log flush is asynchronous from writes
-
- Closed
-
- related to
-
SERVER-20617 wt_nojournal_toggle.js failing intermittently in noPassthrough_WT
-
- Closed
-
-
SERVER-17489 in bulk ops, only mark last operation with commit=synchronous
-
- Closed
-