[SERVER-26108] dbclient_rs_test is the slowest test. Created: 14/Sep/16 Updated: 06/Dec/17 Resolved: 01/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2017-11-13 |
| Participants: |
| Description |
|
dbclient_rs_test in master takes 3m9s on my machine (compiled opt on). This is by far the slowest of all the unittests. All the time difference can be attributed to one subtest, AllNodesDown. In 3.2 it takes 5 sec, in master, 145 sec. Is this affecting performance of replica set monitor, or does the test simply need retooling? |
| Comments |
| Comment by Githook User [ 01/Nov/17 ] |
|
Author: {'name': 'Mathias Stearn', 'username': 'RedBeard0531', 'email': 'mathias@10gen.com'}Message: |