- Medium: It contributes to significant difficulty to complete my task, but I can work around it.
When analyzing flow with opentelemetry trace we noticed that the first real remote call to actor takes a long time (700 ms) (we have a remote call before just to understand that the actor is up)
The image shows two flows, the first is the the first call, the second image is from one of the following spans.
We see around 2 such calls per batch of new actors. Can’t understand any reason except that we have 2 threads that call remote actor functions
Our driver is outside the cluster
I need to understand what this /ray.rpc.rayletdriver/getobject to understand it won’t affect the overall performance.
service.name driver process name