[SERVER-16476] Improvement in certain mongo-perf test cases Created: 09/Dec/14  Updated: 15/May/15  Resolved: 15/May/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.8.0-rc2
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Problem

Under 2.8.0-rc2 with WT storage engine there are a few mongo-perf tests that show further optimization could be consider, when considered against mmapv1.

Update.MmsIncShallow1
Update.MmsIncShallow2
Update.MmsIncDeep1
Update.MmsIncDeepSharedPath2
Update.MmsIncDeepSharedPath3
Update.MmsIncDeepDistinctPath2
Update.MmsIncDeepDistinctPath3
Update.FieldAtOffset

Each of these tests is a single contended document, with 512k fields, where one field is being updated.

Reproduce

python ./benchrun.py -f testcases/*.js --trialTime 5 --trialCount 1 -l mytest --nodyno --testFilter "['Update.MmsIncShallow1']" -m 1 -c 1 -t 12


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