-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Service Arch
-
0
The new, asynchronous implementation of buildInfo (see here) imposes some performance overhead on standalone in-memory benchmarks. The source of this overhead could be a mix of the following:
- The context switch to schedule the rest of continuation on the buildInfo executor (see here).
- The number of threads used to run asynchronous buildInfo commands (see here).
- The cost of binding the client strand to the executor thread to serve buildInfo requests (see here). This is equivalent to the time it takes to construct the future-chain and releasing the client strand in here.
The acceptance criteria for this ticket is to reduce the cost of asynchronous buildInfo for the following benchmarks: