BeagleBrainz
pointed out
, that for a latency test "one should stress the computer". This is also mentioned
here
. BeagleBrainz stated also, that this means io load, like disc access, like opying large files around etc.
So far, my script does none of this. It collects data of the hardware used and invokes a latency test with or without a base thread, depending users wish and/or if a parallel port is detected.
While I did exactly that (ripping a dvd to hd) for wheezy based install, I did not consider this being required to get "realistic" latency data when writing the script. It was my believe, that LnuxCNC, once loaded from disc, does by far most of its duties in Ram. It would read the gcode file yes, but these files almost never go into the GB range. The largest gcode file I have is ~22MB.
Prior to adding heavy disc io, I would like to understand the reasoning, as why this is really needed to get reliable, repeatable latency data for the - say - database in
forum.linuxcnc.org/18-computer/39371-res...se-with-linuxcncthis
thread.
So, kindly give me a hand, let me know why it is needed and - most important - what is needed.
Greez
chris