[SERVER-11498] sorter_test takes unreasonable amount of time unless built with optimization Created: 31/Oct/13 Updated: 11/Jul/16 Resolved: 05/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
We shouldn't require developers to build with --opt=on to run the unit tests, and sorter_test takes way way to long (more than 10 minutes?) if not built like that. We need to find a way to make this test reasonably fast, either by intelligent use of mocks to not need to use such large sizes to trigger 'spilling', or by explicitly always compiling this one file with optimization enabled (either via scons, or some sort of #pragma optimize on like solution, if there is one for clang and gcc (doesn't look like clang has this yet)). It is not reasonable to require developers to always pass --opt=on if they want a --dbg build. |
| Comments |
| Comment by Githook User [ 05/Feb/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |