[SERVER-42286] Return connections inline, spawn connections out of line Created: 18/Jul/19 Updated: 29/Oct/23 Resolved: 24/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc5, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Security 2019-07-15, Service Arch 2019-08-12 | ||||
| Participants: | |||||
| Description |
|
It turns out that both get and the conn dtor effectively avoid the executor queue when they run inline. This is desirable because it means any given command can start sooner. That said, spawning connects is only necessary rarely and always slow when it is needed. |
| Comments |
| Comment by Githook User [ 24/Jul/19 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |
| Comment by Githook User [ 24/Jul/19 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |