[SERVER-17407] Significant performance degradation between SA mongod to replica set on insert only workload Created: 27/Feb/15  Updated: 14/Sep/15  Resolved: 14/Sep/15

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.0.0-rc11
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eitan Klein Assignee: Chung-yen Chang
Resolution: Incomplete Votes: 0
Labels: 28qa, wttt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File InsertOnlySAvsReplSetWindows.png     Microsoft Word ReplicaSetMember (1).csv     Text File ReplicaSetMember - MongoStat.txt     Text File ReplicaSetMemberLog.txt     Microsoft Word SA.csv     Text File SA.txt     PNG File Screen Shot 2015-03-18 at 5.13.21 PM.png     PNG File Screen Shot 2015-03-20 at 12.40.47 PM.png    
Issue Links:
Related
related to SERVER-16575 intermittent slow inserts with WiredT... Closed
Operating System: ALL
Sprint: RPL 1 04/03/15
Participants:

 Description   

v3.0.0-Rc11

Environment:

• Replica set with 2 nodes vs. stand alone mongod
• The measurement has been taken from the same machine, when it was configured as replica set the machine worked as primary.
• Windows 2012 magnatic drive

Workload:
• Used hammer.mongo to do insert only workload

Measured a signficent amount of performance degrdation between Stand Alone to Replica set

Measurements Stand alone performance Replica set (2 members) Performance difference
IO Write throughput 12 K operations/sec 2 K operations/sec -84%
MongoStat info 15 K inserts/sec 2 K insert/sec ..TBD..
Context switchs 36 K 4.5K  

More details @ https://docs.google.com/a/10gen.com/document/d/1RyvsyEs0HygsSZJ1hs_02yWxR-NEzjRNi6jf6I38GSo/edit?usp=sharing

will work to identify the bottleneck



 Comments   
Comment by David Daly [ 19/Aug/15 ]

A much smaller regression is visible on mongo-perf in evergreen. Can compare standalone and 1 node repl

There's also https://jira.mongodb.org/browse/SERVER-19975 but that seems like it's probably a later issue.

Generated at Thu Feb 08 03:44:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.