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. |
Beta Was this translation helpful? Give feedback.
-
RpcAdapaterEngine break-down:
|
Beta Was this translation helpful? Give feedback.
-
misc:
|
Beta Was this translation helpful? Give feedback.
-
One-way RPC hello performance
>=16384 messages:
|
Beta Was this translation helpful? Give feedback.
-
channel performance (one-way): hypercore pair
no affinity set:
|
Beta Was this translation helpful? Give feedback.
-
channel performance (round-trip): hypercore pair
no affinity set:
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
minstant is very helpful. The overhead itself is super low (as low as 7-8 ns).
The overhead comes from two major sources
|
Beta Was this translation helpful? Give feedback.
-
On the other side, in check_input_queue
|
Beta Was this translation helpful? Give feedback.
-
Just removing all spans, |
Beta Was this translation helpful? Give feedback.
-
Where there is no work |
Beta Was this translation helpful? Give feedback.
-
mRPC engine mainloop:
In |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
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-debug
branch.Beta Was this translation helpful? Give feedback.
All reactions