You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a pingpong RPC on UCX/IB costs 20-30us. We expect to optimize it to ~5us.
The main overhead is coroutine switch: Due to the limitation of UCX, all UCX operations must run on a single thread. So a send request have to be sent from user coroutine to the network coroutine, and a received message have to be sent from the network coroutine to user coroutine. A RPC handler can be directly called from the network coroutine, but now it has 2 extra switches.
The text was updated successfully, but these errors were encountered:
Currently a pingpong RPC on UCX/IB costs 20-30us. We expect to optimize it to ~5us.
The main overhead is coroutine switch: Due to the limitation of UCX, all UCX operations must run on a single thread. So a send request have to be sent from user coroutine to the network coroutine, and a received message have to be sent from the network coroutine to user coroutine. A RPC handler can be directly called from the network coroutine, but now it has 2 extra switches.
The text was updated successfully, but these errors were encountered: