-
Type: Improvement
-
Resolution: Fixed
-
Priority: Unknown
-
Affects Version/s: 1.9.1
-
Component/s: None
-
None
This is how the top of allocation profile looks like in one of our batch processing services.
We use sharded cluster, pool of mongos services, and drvier 1.9.1.
It seems that, in our case at least, this selection in a no-op (all candidates are Mongos), but the allocation burden is very considerable.
- related to
-
GODRIVER-2626 PR: further optimize selectByKind for special case of all fitting servers
- Closed
-
GODRIVER-2627 PR: optimize latency selector
- Closed
-
GODRIVER-2628 PR: optimize allocations in selectServerFromDescription
- Closed