search

ammarm08 / quasimodo

Benchmark NodeJS programs against each other (CPU, memory, loadtesting)
0 stars 0 forks source link

On load tests, ab/loadtest-calculated test length differs from time/gtime-calculated test length #9

Closed ammarm08 closed 7 years ago

ammarm08 commented 7 years ago

This is due to calling sleep 2 immediately after starting the node process, and only after doing this will the loadtest start.

Time discrepancy is pretty much exactly 2 sec.

Find a way to allow for this sleep 2 (so that the node process can "warm up") without it affecting the overall wall clock measurement by time/gtime.

Alternate solution: get rid of clock altogether.