To know when and where the problems begin.
And the time of dstat, to not look the stats blindly.
Expected Behavior
--------------------------------------------------------------------------------
Started plaintext concurrency 256
2018/02/06 19:10:00 | 1517943552.195 Dstat time
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Started plaintext concurrency 512
2018/02/06 19:10:20 | 1517943552.195 Dstat time
--------------------------------------------------------------------------------
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
--------------------------------------------------------------------------------
Started plaintext concurrency 1024
2018/02/06 19:10:30 | 1517943552.195 Dstat time
--------------------------------------------------------------------------------
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
--------------------------------------------------------------------------------
Stopping framework-x
--------------------------------------------------------------------------------
Actual Behavior
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
Server php: 2018/02/06 19:10:00 [alert] 32170#0: 1024 worker_connections are not enough
--------------------------------------------------------------------------------
Stopping framework-x
--------------------------------------------------------------------------------
In terminal
tfb --m benchmark
When benchmarking locally, if your are looking htop, Dstats, ... you don't know what is doing the benchmark.
Only when finish a test, show the json results, without any information about which test.
Also the json don't show the req/s, easier to check with different durations than the total requests.
Perhaps will be better to show the wrk results.
WARNING:root:Framework http4k does not define a default test in benchmark_config.json
fatal: Not a git repository (or any of the parent directories): .git
WARNING:root:Framework http4k does not define a default test in benchmark_config.json
WARNING:root:Framework http4k does not define a default test in benchmark_config.json
PD: What gui do you use to look at the stats of dstat?
In out.txt
To know when and where the problems begin. And the time of dstat, to not look the stats blindly.
Expected Behavior
Actual Behavior
In terminal
tfb --m benchmark
When benchmarking locally, if your are looking htop, Dstats, ... you don't know what is doing the benchmark. Only when finish a test, show the json results, without any information about which test. Also the json don't show the req/s, easier to check with different durations than the total requests. Perhaps will be better to show thewrk
results.Expected Behavior
Actual Behavior
Also fix Framework http4k
To not show in every bench this:
PD: What gui do you use to look at the stats of dstat?