Timing RPC calls

#1

I would like a easy way to log how long each RPC call is taking, at least as far as the crossbar server is concerned.
Does anyone have any ideas on the best way to go about this?

0 Likes

#2

From the view of a caller, just start a timer and check how much time has elapsed until the result is received.

If you want to measure the delay from caller to callee under realistic network conditions, you may run into time sync issues between the machines. For NTP over the public internet, you can only get sync in the order of 10s of milliseconds (at least according to Wikipedia). When I look at our PubSub demo (https://demo.crossbar.io/pubsub/index.html), which measures latency for a publish, I get a round-trip time of ~12 ms between the office and the demo instance in Frankfurt (~500 km round-trip distance). Without a better time sync than NTP, the latency of the Crossbar.io instance in that is well below your measuring accuracy.

ยทยทยท

Am Freitag, 5. Februar 2016 01:22:57 UTC+1 schrieb craig@dialog.fit:

I would like a easy way to log how long each RPC call is taking, at least as far as the crossbar server is concerned.
Does anyone have any ideas on the best way to go about this?

0 Likes