lat_rpc hostname [udp|tcp]
This benchmark may be compared to the TCP and UDP forms of the same benchmark to accurately see the cost of using RPC versus the cost of using plain old TCP or UDP sockets. It is worth noting that the RPC form is passing back and forth a single byte, not some long complicated record.
lat_rpc has three forms of usage: as a server (-s), as a client (lat_rpc localhost), and as a shutdown (lat_rpc -localhost).
The client form may specify the protocol over which the RPCs are performed. The default is ``udp''.
RPC/udp latency using localhost: 1344 microseconds RPC/tcp latency using localhost: 2089 microseconds