rvlat
Command
Syntax
rvlat  { cli | srv }
       [-service service ]
       [-network network ]
       [-daemon daemon ]
       [-sample response_rate]
       [-messages m ]
       [-time t ]
       [-size size ]
       [-batch batch_size ]
       [-interval interval ]
       [-inbox]
       [-vectored]
       [-terse]
       [-datapoints]
       [-spikes threshold ]
       [-w filename]
       [-h]
                Purpose
rvlat measures network latency. The client sends request messages to the server, and reports statistics to stdout and stderr. The server responds to client requests immediately.
Outline
Each run consists of these steps:
Procedure
| 1. | Send a run of messages. | 
| 2. | Output statistics that measure the performance of the sender. | 
| 3. | Output statistics that measure the performance of each receiver (if any). | 
| 4. | Output a summary of error advisories pertaining to the sender. | 
| Parameter | Description | ||||||
| Mode Parameters | |||||||
| 
 | Run a client instance. | ||||||
| 
 | Run a server instance. | ||||||
| Parameters that Apply to Both Client and Server | |||||||
| 
 See Service Selection. When absent, the default value is  | |||||||
| 
 See Network Selection. When absent, the default value is the multicast address | |||||||
| The  See Daemon Client Socket—Establishing Connections. You can specify a daemon on a remote computer. For details, see Remote Daemon. However, the program cannot start a remote daemon automatically—you must start it manually on the remote computer. Note that using a remote daemon could increase latency. When absent, the program finds the local daemon on TCP socket  | |||||||
| Sending When  When present,  When absent,  Receiving When  When present,  When absent,  | |||||||
| 
 | When present, output a parameter usage list to  | ||||||
| Server-Only Parameters | |||||||
| For background information, see Measuring Technique. When present, the server uses a random number generator to select a subset of requests to which it responds, while ignoring all the rest. The value of  When absent, the server responds to 100% of the request messages it receives. We do not recommend using  | |||||||
| Client-Only Parameters that Control Measuring | |||||||
| When present,  When absent, the default is a run of 10,000 messages. | |||||||
| When present,  When absent, the default behavior sends a specific number of messages (rather than running for a specific time). | |||||||
| 
 Use this size to model application data rates. This size does not include message header data nor packet overhead. When absent, the default is 0 payload bytes in each message. | |||||||
| When present,  When absent,  | |||||||
| When  When absent, the default pause is 1 second. In serial mode (that is, when  | |||||||
| 
 | When present, the client sends request messages to an inbox on the server (using point-to-point protocols). The server responds to an inbox on the client. When absent, the client sends request messages to a multicast subject (using either multicast or broadcast protocols, as specified in the  | ||||||
| Client-Only Parameters that Control Output | |||||||
| The client can output two types of reports: 
 
 The two types of report include the same information, and both are in CSV format. When this option is present,  When absent,  | |||||||
| When present,  Caution: This option can generate an unwieldy volume of data. | |||||||
| When present,  | |||||||
| 
 | When present,  If the file is not empty,  Output to  | ||||||