[SERVER-48159] Reduce the inline cost of isConnected() Created: 12/May/20 Updated: 08/Jan/24 Resolved: 24/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Amirsaman Memaripour |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Service arch 2020-05-18, Service arch 2020-06-01, Service arch 2020-06-15, Service arch 2020-06-29 | ||||
| Participants: | |||||
| Description |
|
About 4% of the samples from running a 100% read workload (YCSB) against mongos are collected from isConnected. We should investigate ways to reduce this cost or move it out of the critical path. |
| Comments |
| Comment by Githook User [ 24/Jun/20 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |
| Comment by David Daly [ 13/May/20 ] |
|
amirsaman.memaripour we may have a bad baseline comparison for you on the mixed workloads. I took a look and there's a suspiciously large drop on that commit, and it's the last to have run. I've restarted it to see. I was fascinated by those huge results you had. |