Supported payload configuration for TCP/TLS queries

[eoregua]

Hi,

I'm using using fortio to perform few benchmarking TCs for my service (based on envoy). I'm mainly interested to measure performance for pure TCP and TLS (mutual and simple) connections.

Basically I collected the first results testing tcp and tls performance without explicitely set the payload size:

e.g from fortio client:

For TCP, CMD:

fortio load -qps 1000 -c 8 -t 60s tcp://fortio-server-1:8078

For mTLS, CMD:

fortio load -a -grpc -ping -cert server.pem -key serverkey.pem -cacert cacert.pem  -qps 1000 -c 8 -t 60s tcp://fortio-server-1:8079

If I don't set anything related to the payload in the fortio client and fortio server, what is default size for the payload in the TCP and TLS queries?

I tried to specify a file as payload input for the CMD apply from fortio client but I noticed that increasing the size of payload over a certain value I'm able to see some issues (TCP short read, bytes received < byte sent).

Is there any reason for it? Any indication to setup correctly fortio client/server changing the payload size?

The results below are obtained only using fortio client/server without adding anything in the middle to prevent any question on the service in the middle and just focus on this item (supported payload configuration).

Thanks for the support!

Details from TCs:

bash-4.4# dd if=/dev/urandom of=testsize.txt bs=20KB count=1
1+0 records in
1+0 records out
20000 bytes (20 kB, 20 KiB) copied, 0.000262156 s, 76.3 MB/s

bash-4.4# fortio load -payload-file testsize.txt -qps 1 -c 8 -t 5s tcp://fortio-server-1:8078 
Fortio 1.21.2 running at 1 queries per second, 16->16 procs, for 5s: tcp://fortio-server-1:8078
09:49:17 I tcprunner.go:222> Starting tcp test for tcp://fortio-server-1:8078 with 8 threads at 1.0 qps
09:49:17 W periodic.go:346> Lowering number of threads - total call 5 -> lowering from 8 to 2 threads
Starting at 1 qps with 2 thread(s) [gomax 16] for 5s : 2 calls each (total 4)
09:49:21 I periodic.go:693> T001 ended after 4.001069169s : 2 calls. qps=0.49986638958802765
09:49:21 I periodic.go:693> T000 ended after 4.001242434s : 2 calls. qps=0.49984474397384143
Ended after 4.001269568s : 4 calls. qps=0.99968
Sleep times : count 2 avg 3.9997337 +/- 2.366e-05 min 3.999710059 max 3.999757371 sum 7.99946743
Aggregated Function Time : count 4 avg 0.0002429805 +/- 0.0001112 min 0.000161848 max 0.000434471 sum 0.000971922
# range, mid point, percentile, count
>= 0.000161848 <= 0.000434471 , 0.000298159 , 100.00, 4
# target 50% 0.000252722
# target 75% 0.000343597
# target 90% 0.000398121
# target 99% 0.000430836
# target 99.9% 0.000434108
Sockets used: 8 (for perfect no error run, would be 2)
Total Bytes sent: 240000, received: 240000
tcp OK : 4 (100.0 %)
All done 4 calls (plus 8 warmup) 0.243 ms avg, 1.0 qps
bash-4.4# fortio load -payload-file testsize.txt -qps 10 -c 8 -t 5s tcp://fortio-server-1:8078 
Fortio 1.21.2 running at 10 queries per second, 16->16 procs, for 5s: tcp://fortio-server-1:8078
09:49:34 I tcprunner.go:222> Starting tcp test for tcp://fortio-server-1:8078 with 8 threads at 10.0 qps
Starting at 10 qps with 8 thread(s) [gomax 16] for 5s : 6 calls each (total 48)
09:49:39 I periodic.go:693> T006 ended after 4.801241504s : 6 calls. qps=1.2496767752676663
09:49:39 I periodic.go:693> T004 ended after 4.801274664s : 6 calls. qps=1.24966814437592
09:49:39 I periodic.go:693> T005 ended after 4.801368682s : 6 calls. qps=1.2496436739993715
09:49:39 I periodic.go:693> T007 ended after 4.801391572s : 6 calls. qps=1.2496377164882482
09:49:39 I periodic.go:693> T000 ended after 4.80137162s : 6 calls. qps=1.2496429093318129
09:49:39 I periodic.go:693> T001 ended after 4.801406516s : 6 calls. qps=1.2496338270891787
09:49:39 I periodic.go:693> T002 ended after 4.801449599s : 6 calls. qps=1.2496226142308404
09:49:39 I periodic.go:693> T003 ended after 4.801377867s : 6 calls. qps=1.249641283440356
Ended after 4.801663054s : 48 calls. qps=9.9965
Sleep times : count 40 avg 0.95910463 +/- 0.0002652 min 0.958757139 max 0.959553752 sum 38.364185
Aggregated Function Time : count 48 avg 0.00033936827 +/- 0.0001359 min 0.000132744 max 0.000712552 sum 0.016289677
# range, mid point, percentile, count
>= 0.000132744 <= 0.000712552 , 0.000422648 , 100.00, 48
# target 50% 0.00041648
# target 75% 0.000564516
# target 90% 0.000653338
# target 99% 0.000706631
# target 99.9% 0.00071196
Sockets used: 8 (for perfect no error run, would be 8)
Total Bytes sent: 1120000, received: 1120000
tcp OK : 48 (100.0 %)
All done 48 calls (plus 8 warmup) 0.339 ms avg, 10.0 qps

bash-4.4# fortio load -payload-file testsize.txt -qps 100 -c 8 -t 5s tcp://fortio-server-1:8078 
Fortio 1.21.2 running at 100 queries per second, 16->16 procs, for 5s: tcp://fortio-server-1:8078
09:49:52 I tcprunner.go:222> Starting tcp test for tcp://fortio-server-1:8078 with 8 threads at 100.0 qps
Starting at 100 qps with 8 thread(s) [gomax 16] for 5s : 62 calls each (total 496)
09:49:57 I periodic.go:693> T005 ended after 4.960898419s : 62 calls. qps=12.497736249253363
09:49:57 I periodic.go:693> T004 ended after 4.961098966s : 62 calls. qps=12.497231041933624
09:49:57 I periodic.go:693> T002 ended after 4.960977292s : 62 calls. qps=12.497537551719962
09:49:57 I periodic.go:693> T001 ended after 4.961126402s : 62 calls. qps=12.49716192979999
09:49:57 I periodic.go:693> T000 ended after 4.961144258s : 62 calls. qps=12.497116950393664
09:49:57 I periodic.go:693> T007 ended after 4.961102452s : 62 calls. qps=12.497222260549275
09:49:57 I periodic.go:693> T006 ended after 4.9611123s : 62 calls. qps=12.497197453079222
09:49:57 I periodic.go:693> T003 ended after 4.961103963s : 62 calls. qps=12.497218454278944
Ended after 4.961310614s : 496 calls. qps=99.974
Sleep times : count 488 avg 0.080302189 +/- 0.0004773 min 0.072595594 max 0.081108108 sum 39.1874681
Aggregated Function Time : count 496 avg 0.00034049597 +/- 0.0003593 min 0.000102902 max 0.008111951 sum 0.168886
# range, mid point, percentile, count
>= 0.000102902 <= 0.001 , 0.000551451 , 99.80, 495
> 0.008 <= 0.00811195 , 0.00805598 , 100.00, 1
# target 50% 0.000551451
# target 75% 0.000776633
# target 90% 0.000911743
# target 99% 0.000992809
# target 99.9% 0.00805642
Sockets used: 8 (for perfect no error run, would be 8)
Total Bytes sent: 10080000, received: 10080000
tcp OK : 496 (100.0 %)
All done 496 calls (plus 8 warmup) 0.340 ms avg, 100.0 qps
bash-4.4# 

bash-4.4# fortio load -payload-file testsize.txt -qps 1000 -c 8 -t 5s tcp://fortio-server-1:8078 
Fortio 1.21.2 running at 1000 queries per second, 16->16 procs, for 5s: tcp://fortio-server-1:8078
09:50:09 I tcprunner.go:222> Starting tcp test for tcp://fortio-server-1:8078 with 8 threads at 1000.0 qps
Starting at 1000 qps with 8 thread(s) [gomax 16] for 5s : 625 calls each (total 5000)
09:50:14 I periodic.go:693> T003 ended after 5.000940387s : 625 calls. qps=124.9764947458071
09:50:14 I periodic.go:693> T001 ended after 5.001063674s : 625 calls. qps=124.9734138058087
09:50:14 I periodic.go:693> T007 ended after 5.001010195s : 625 calls. qps=124.974750226439
09:50:14 I periodic.go:693> T005 ended after 5.001106387s : 625 calls. qps=124.97234644410695
09:50:14 I periodic.go:693> T004 ended after 5.00109821s : 625 calls. qps=124.97255077900179
09:50:14 I periodic.go:693> T002 ended after 5.001143003s : 625 calls. qps=124.97143145578634
09:50:14 I periodic.go:693> T006 ended after 5.001115123s : 625 calls. qps=124.97212814111018
09:50:14 I periodic.go:693> T000 ended after 5.001148437s : 625 calls. qps=124.97129566802337
Ended after 5.001261795s : 5000 calls. qps=999.75
Sleep times : count 4992 avg 0.0070439925 +/- 0.0003395 min 0.000780146 max 0.007830061 sum 35.1636106
Aggregated Function Time : count 5000 avg 0.00027051068 +/- 0.0001265 min 6.1775e-05 max 0.006219199 sum 1.35255338
# range, mid point, percentile, count
>= 6.1775e-05 <= 0.001 , 0.000530888 , 99.76, 4988
> 0.001 <= 0.002 , 0.0015 , 99.98, 11
> 0.006 <= 0.0062192 , 0.0061096 , 100.00, 1
# target 50% 0.000531922
# target 75% 0.00076709
# target 90% 0.000908191
# target 99% 0.000992851
# target 99.9% 0.00163636
Sockets used: 8 (for perfect no error run, would be 8)
Total Bytes sent: 100160000, received: 100160000
tcp OK : 5000 (100.0 %)
All done 5000 calls (plus 8 warmup) 0.271 ms avg, 999.7 qps

bash-4.4# dd if=/dev/urandom of=testsize.txt bs=200KB count=1
1+0 records in
1+0 records out
200000 bytes (200 kB, 195 KiB) copied, 0.00159249 s, 126 MB/s

bash-4.4# fortio load -payload-file testsize.txt -qps 1 -c 8 -t 5s tcp://fortio-server-1:8078 
Fortio 1.21.2 running at 1 queries per second, 16->16 procs, for 5s: tcp://fortio-server-1:8078
09:50:54 I tcprunner.go:222> Starting tcp test for tcp://fortio-server-1:8078 with 8 threads at 1.0 qps
09:50:54 W periodic.go:346> Lowering number of threads - total call 5 -> lowering from 8 to 2 threads
Starting at 1 qps with 2 thread(s) [gomax 16] for 5s : 2 calls each (total 4)
09:50:58 I periodic.go:693> T000 ended after 4.001062527s : 2 calls. qps=0.49986721939574424
09:50:58 I periodic.go:693> T001 ended after 4.001142591s : 2 calls. qps=0.49985721691066826
Ended after 4.001171696s : 4 calls. qps=0.99971
Sleep times : count 2 avg 3.9995992 +/- 3.769e-05 min 3.999561551 max 3.999636938 sum 7.99919849
Aggregated Function Time : count 4 avg 0.0004927475 +/- 0.0001557 min 0.000311537 max 0.000712024 sum 0.00197099
# range, mid point, percentile, count
>= 0.000311537 <= 0.000712024 , 0.000511781 , 100.00, 4
# target 50% 0.000445033
# target 75% 0.000578528
# target 90% 0.000658626
# target 99% 0.000706684
# target 99.9% 0.00071149
Sockets used: 12 (for perfect no error run, would be 2)
**Total Bytes sent: 2400000, received: 796096**
tcp short read : 4 (100.0 %)
All done 4 calls (plus 8 warmup) 0.493 ms avg, 1.0 qps

edited: use ``` not other quotes for blocks

[ldemailly]

The default tcp:// load is 24 bytes

fortio load -c 1 -n 1 tcp://localhost:8078/
[...]
Total Bytes sent: 24, received: 24

As you found you can change the payload using -payload, -payload-size, -payload-file:

$ fortio load -payload-size 2048 -c 1 -n 1 tcp://localhost:8078/
[...]
Total Bytes sent: 2048, received: 2048

But it does seem there is an issue for payloads > 32768. (32k)

[ldemailly]

filled #547 for payloads over 32k

[ldemailly]

bug is fixed in https://github.com/fortio/fortio/releases/tag/v1.26.0 and I hope I answered your questions