Repository navigation
Koala performance analysis #110
Replies: 13 comments 18 replies
|
Preliminary analysis on engine mainloop exeuction time When num_works > 0:
When num_works == 0:
These numbers are measured using std::time::Instant::now().elapsed(), which it self has about ~20ns exeuction time. |
|
RpcAdapaterEngine break-down:
|
|
misc:
|
|
One-way RPC hello performance
>=16384 messages:
|
|
channel performance (one-way): hypercore pair
no affinity set:
|
|
channel performance (round-trip): hypercore pair
no affinity set:
|
|
minstant is very helpful. The overhead itself is super low (as low as 7-8 ns).
The overhead comes from two major sources
|
|
On the other side, in check_input_queue
|
|
Just removing all spans, |
|
Where there is no work |
|
mRPC engine mainloop: In |
|
ReclaimRecvBuf is a super-slow operation. This operation may not be on the critical path. There are several potential ways to reduce this overhead.
Fusing small messages into one work request also helps. |



Uh oh!
There was an error while loading. Please reload this page.
This discussion is used to track koala's performance analysis, identify bottlenecks and potential solutions. The performance analysis is currently conducted on
wyj-debugbranch.All reactions