[SERVER-26129] Investigate perf overhead of collation Created: 15/Sep/16 Updated: 13/Oct/16 Resolved: 13/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | David Storch |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Query 2016-10-10, Query 2016-10-31 | ||||||||
| Participants: | |||||||||
| Description |
|
We should write some performance tests to investigate the performance of a query using a collation that involves lots of string comparisons, and compare it to the same without a collation. We expect the worst cases to be in SORT stages and filters which involve string comparisons and are not provided by an index. |
| Comments |
| Comment by David Storch [ 13/Oct/16 ] |
|
Performance regression tests have been added to mongo-perf. See tests with the "collation" label in the following files: https://github.com/mongodb/mongo-perf/blob/develop/testcases/simple_query.js Initial performance testing shows that nearly all of the additional work spent for collation is for generating collator comparison keys. See SERVER-26621 for an idea of how to spend less time building comparison keys. I'm closing this ticket as "Won't Fix", since there is no specific further development work planned. |