[SERVER-9455] mongodump'ing on Windows: performance regression from 2.0 to 2.2 to 2.4 Created: 25/Apr/13  Updated: 26/Apr/13  Resolved: 26/Apr/13

Status: Closed
Project: Core Server
Component/s: Performance
Affects Version/s: 2.4.2
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Nicholas Tang Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 64 bit 2008 builds


Issue Links:
Duplicate
duplicates SERVER-9242 serverStatus workingSet and indexCoun... Closed
Related
is related to SERVER-9458 Very slow page faulting on windows on... Closed
Operating System: Windows
Steps To Reproduce:
  • Do a mongodump on a medium to large sized dataset against a 2.4.x server
Participants:

 Description   

Running a mongodump against a Windows MongoDB server has gotten significantly slower in 2.4.x.

Testing shows that this is not a mongodump client issue: running mongodump 2.2 or 2.0 against a 2.4 database shows essentially the same performance degradation. Something in the default server on Windows (64 bit 2008 build) has made mongodumps much slower.



 Comments   
Comment by Tad Marshall [ 26/Apr/13 ]

The incorrect caching of an uncalculated value of blockCheckSupported was the reason for the performance degradation. See SERVER-9242.

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