p4 ping
Test network performance.
Syntax
p4 [g-opts] ping [-f] [-p pausetime] [-c count] [-t transmittime] [-i iterations] [-s sendsize] [-r receivesize]
Description
p4 ping simulates
Helix Server
network traffic by sending messages from the versioning service to the
Helix Server
application and back, and times the round trips. Round-trip times are
reported in milliseconds. Because the round-trip time is typically too
fast to measure for a single message, you can specify a message
count
per test.
Options
|
Number of messages per test. |
|
Flood mode: the service transmits continuously, sending the next message without waiting for the Helix Server application to confirm receipt of the prior message. |
|
Repeat the test for the specified number of
|
|
Pause for |
|
Size of the user-to-service message, up to a maximum value of 100,000 bytes. |
|
Size of the service-to-user message, up to a maximum value of 10,000,000 bytes. |
|
Transmit data for |
|
See Global options. |
Usage Notes
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
N/A |
N/A |
available to an operator user |
- Like the operating system’s counterpart,
p4 ping
can flood the network with traffic.