Script for automated testing of computer latency.

tommylight: thanks for making the therad with the script results sticky

greez
chris

In this post, forum member my1987toyota wrote, that he could not get the script torun under wheezy (linuxcnc 2.7).

I checked it on a wheezy based pc. There is a number of stuff that needs to be added in the script. These things require specific solutions for wheezy. As I lack of time for now, I will not alter the script to run under wheezy too. I might do that later though. So, for time being, the script will *not* run under wheezy.

@tommylight: could you kindly add a corresponding hint in your initial post? tia

greez
chris

Hi all

I am currently updating the script a bit. My intentions are:

• some debugging in prettier / clearer outputs
• add code to list parports and maybe their current config values like address, io etc.
• add a hint what output to place to the results thread
• option to just get the hw data and skip latency test
• option to just do latency test with latency summary only
• skip the .lat file by default but leave an option to have it generated all the same

I got thursday off, so I could work on some more stuff if desired. So, let the ideas come.

greez chris

Good idea, I will look into that.

Will the script become usable on Debian Wheezy with the upcoming update? I'd like to test a new computer with bootable USB stick, and the current version for download is based on Wheezy.

JKAVS

I migrated my two wheezy based machines to buster in a wink of an eye. I think everyone can do it nicely. Wheezy is outdated and not being maintained. An updated script would be +/- just for wheezy and that will +/- double the effort. I honestly think it is not worth it. Thus, I will not update it to run under wheezy, sorry.

greez
chris

Hi all

Took - well, really - some time more than I thought it would ...

After using the latest 2.8.0 iso from here , and running my script, I faced some weird issues like glxgears not being (kind of) randomly resized, I saw myself in front of a heap of rework.

I added the following:

• detection of parports
• min/max logging of cpu temperatures (to give a hint on cpu throttling)
• better/more specific output regarding hard or software confguration/
• hopefully more stable behaviour

@tommylight:
Kindly replace the link in your first post with the script attached.