warp client

Start a Warp client instance to participate in distributed benchmark operations.

warp client [FLAGS] [LISTEN_ADDRESS]

warp client 192.168.1.101:7761

The network address and port where the client listens for coordinator connections. Specify the address in the format host:port or ip:port.

The default port is 7761 if not specified. Omit this parameter entirely to listen on all interfaces using the default port.

Example addresses include 192.168.1.101:7761 or :8080.

Default: false

Disable color output in the terminal. The default behavior displays colored output for better readability. Use this flag when redirecting output to files or when terminal colors cause display issues.

Example:

warp client --no-color

Default: false

Enable detailed debug output for troubleshooting. The default behavior shows only standard operational messages. Use this flag to see internal operations and diagnostic information.

Example:

warp client --debug

Default: false

Disable TLS certificate verification for S3 endpoint connections. The default behavior validates TLS certificates for secure connections. Use this flag only for testing with self-signed certificates or development environments.

Example:

warp client --insecure

Default: false

Install shell autocompletion for Warp commands. The default behavior does not modify shell configuration. Use this flag once to enable tab completion in your shell environment.

This flag supports bash, zsh, and fish shells.

Example:

warp client --autocompletion

The client mode enables distributed benchmarking load generation from multiple machines. This architecture allows Warp to generate higher loads than a single machine can produce.

Start client instances on each machine designated for load generation. Then run a benchmark command on the coordinator machine with the --warp-client flag to connect to all clients.

# On each client machine
warp client

# On coordinator machine
warp get --warp-client client1:7761,client2:7761,client3:7761 --access-key YOUR_ACCESS_KEY --secret-key YOUR_SECRET_KEY

The coordinator connects to each client and distributes the benchmark workload. All clients execute the same benchmark parameters simultaneously. The coordinator collects and aggregates results from all clients into a single comprehensive report.

For complete information about distributed benchmarking architecture, deployment strategies, network requirements, and best practices, see the Distributed benchmarking documentation.

Start a client listening on all interfaces with the default port:

warp client

The client listens on port 7761 and accepts connections from any network interface.

Start a client listening on a specific IP address and port:

warp client 192.168.1.101:7761

This configuration listens only on the specified interface. Use this approach when the machine has multiple network interfaces.

Start a client on a non-default port:

warp client :8080

The client listens on port 8080 instead of the default 7761. Remember to specify the custom port when connecting from the coordinator.

Start three clients on different machines:

# On machine 1
warp client 192.168.1.101:7761

# On machine 2
warp client 192.168.1.102:7761

# On machine 3
warp client 192.168.1.103:7761

Run the benchmark from the coordinator:

warp get --host s3.example.com:9000 \
  --access-key ACCESS_KEY \
  --secret-key SECRET_KEY \
  --warp-client 192.168.1.101:7761,192.168.1.102:7761,192.168.1.103:7761 \
  --duration 5m \
  --concurrent 100

The coordinator distributes the workload across all three clients. Each client executes the GET benchmark with 100 concurrent operations. The coordinator aggregates results from all clients into a single report.

Start a client with debug logging enabled:

warp client --debug

This displays detailed information about coordinator connections and benchmark operations. Use debug mode to troubleshoot client connectivity or benchmark execution issues.