[SERVER-20613] Performance Regression on Mongo-perf text tests Created: 17/Sep/15  Updated: 01/Oct/15  Resolved: 01/Oct/15

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

Type: Bug Priority: Major - P3
Reporter: David Daly Assignee: David Daly
Resolution: Duplicate Votes: 0
Labels: mpreg
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-19372 Text query perf regression in commit ... Closed
is related to SERVER-19936 Performance pass on unicode-aware tex... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Performance A (10/08/15)
Participants:

 Description   

Performance regression of 15-30% on

  • Queries.Text.FindSingle
  • Queries.Text.FindSingleCaseSensitive
  • Queries.Text.FindThreeWords
  • Queries.Text.FindThreeWordsCaseSensitive
  • Queries.Text.FindPhrase
  • Queries.Text.FindPhraseCaseSensitive

From 3.1.4.
WT Results
MMAP Results

Regression shows up in MMAP and wiredTiger, although seem to go away on different releases. Need to investigate to understand the regression and the difference.



 Comments   
Comment by David Daly [ 01/Oct/15 ]

After further review, the regression is due almost completely to the effects of SERVER-19372 and SERVER-19936. There was some weirdness in performance behavior around 3.1.5 (came and went) that added some confusion to the analysis. Closing this ticket as a duplicate of the other two.

Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'dalyd', u'name': u'dalyd', u'email': u'david.daly@mongodb.com'}

Message: SERVER-20613: Lower performance target for MP Queries.Text.* until this ticket is resolved
Branch: master
https://github.com/mongodb/mongo/commit/a810c1d50ac35761200516a6f001602f827e3b6f

Comment by David Daly [ 22/Sep/15 ]

This regression is due to combined effects of SERVER-19372, SERVER-19936, plus maybe another 10%. Trying to isolate the remaining 10%.

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