Script for automated testing of computer latency.
03 Nov 2020 22:29 - 03 Nov 2020 22:32 #188275
by seuchato
Replied by seuchato on topic Script for automated testing of computer latency.
Hi all
Took a while, but new version, out soon:
Regarding disc io, CPU and RAM load :
I dug deep into the internet. Came out that large block reads from /dev/urandom into a temporary file provided the largest CPU and Ram load. on a xeon W3635 system with 8 GiBs Ram I got to -p <pidoftask> CPU load is jumping from little above 10% to a full 100%, where must of the time it was above 50%.
The attached "stresstest" can be run alone. as root or sudoed. I have yet to find out a way to weave the subroutine "DiscLoad" into the script in such way, that it terminates gracefully on CTRL-C or script end. Imho CPULoad and RAMLoad subroutines, as well as the low blocksize reads in DiscLoad (proposed 512 bytes) can be put aside. There is now new info to be gained from them.
I'd like to kindly ask the community to check "stresstest" and report what is their conclusion. Meanwhile, I'll continue to integrate "DiscLoad" into the script.
Tia
chris
Took a while, but new version, out soon:
#-----------------------------------------------------------------#
# Todo: (o = open, x = cancelled at least for the time being)
# x skip the .lat file by default but leave an option to have it.
# If, a graphical output will no longer be possible.
# o add a graphical output (one pic = 1000 words)
# o make sure "abort" in UserOptions now really aborts
# o add data on nics for mesa ethernet/hostmot
# o rework mouse keyboard related data, as output is not always
# correct
#-----------------------------------------------------------------
#
# V20201104pre
# . option to just get the hw data and skip latency test (-info)
# . corrected basebin setting if basethread is selected manually
# . added info on Uefi or bios boot
# . more detailed output for RAM data
# . better output regarding blockdevices
# . added script to block pcspkr
# . added write permission check for user to run the very
# latency test
# . added check on *rt* kernel with a warning and prevent
# the very latency test from running
# . better and more compact data on RAM
# o added disc io, CPU and RAM load
# . indent all secondary lines to make reading better Regarding disc io, CPU and RAM load :
I dug deep into the internet. Came out that large block reads from /dev/urandom into a temporary file provided the largest CPU and Ram load. on a xeon W3635 system with 8 GiBs Ram I got to -p <pidoftask> CPU load is jumping from little above 10% to a full 100%, where must of the time it was above 50%.
The attached "stresstest" can be run alone. as root or sudoed. I have yet to find out a way to weave the subroutine "DiscLoad" into the script in such way, that it terminates gracefully on CTRL-C or script end. Imho CPULoad and RAMLoad subroutines, as well as the low blocksize reads in DiscLoad (proposed 512 bytes) can be put aside. There is now new info to be gained from them.
I'd like to kindly ask the community to check "stresstest" and report what is their conclusion. Meanwhile, I'll continue to integrate "DiscLoad" into the script.
Tia
chris
Please Log in or Create an account to join the conversation.
Time to create page: 0.155 seconds