Clarification for --connections

[insekt]

I run

./tcpulse -c --connections 1 XXX.XXX.XXX.XXX:9100

and base on docs

--connections int32          [client mode] Number of concurrent connections to keep
count: Total number of successful connections/requests

expect to get 1 connection but in the results I see

PEER                 CNT        LAT_MAX(µs)     LAT_MIN(µs)     LAT_MEAN(µs)    LAT_90p(µs)     LAT_95p(µs)     LAT_99p(µs)     RATE(/s)  
XXX.XXX.XXX.XXX:9100  500        2243            379             1033            1326            1498            2013            100.03    

CNT=500

If --connections 2
CNT=1000

Please explain why?

[yuuki]

The CNT field represents the total number of messages/requests sent, not connections.

Looking at the key parts of the code:

1. Default rate: rate defaults to 100 requests per second
2. Default duration: duration defaults to 10 seconds
3. Message calculation: In connectPersistent():
   msgsTotal := int64(c.config.Rate) * int64(c.config.Duration.Seconds())

So with defaults:

• --connections 1 → 1 connection established
• Rate = 100 req/s × Duration = 10s = 1000 total messages
• But you're seeing 500, which suggests your test ran for ~5 seconds

With --connections 2:

• 2 connections established
• Each connection sends 500 messages = 1000 total messages

The --connections flag only controls how many concurrent TCP connections are maintained in persistent mode. Each connection sends messages at the specified rate for the full
duration.

To get exactly 1 message, use:

  ./tcpulse -c --connections 1 --rate 1 --duration 1s XXX.XXX.XXX.XXX:9100

[yuuki]

I fixed this issue at #44