Script for automated testing of computer latency.

I am running the lcnc-hw script and I have a few issues/questions/comments.

1. This link in the script is no longer valid: page=' vimeo.com/150574260 '
so I replaced it with this random one.  ' vimeo.com/169701518'2 .

2. I was getting this message and the suggested solution didn't work.
Kernel modules data:
Check if pcspkr is loaded: Yes, may cause bigger latency. 
can be eliminated using:  sudo echo "install pcspkr /bin/true" >/etc/modprobe.d/pcspkr.confI

I ended up adding "blacklist pcspkr" to "/etc/modprobe.d/intel-microcode-blacklist.conf" and that worked.

3. Should I be concerned about these:
.Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

4.  There are never any latency results listed at the end of the .hw file.

5.  What numbers should I be shooting for if I am using a 7i76E?  Are these numbers good? Good enough?  Keep trying?

Thes are the last results in my .lat file. 
598 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
599 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
600 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
601 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
601 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
602 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
603 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us 
603 s  servo min: -80.000 us max:  87.100 us sdev:   4.300 us

I attached my .lat and .hw files.  I will post my results in the proper results page when I get the results that I think are final.




Thanks
John

 

That will do just fine for Mesa ethernet boards.

Johnny
I am currently working on the script and address the issues you report. So, thanks for posting them!

• pcspkr: "etc/modprobe.d/pcspkr.confI" Is there an "l" (ell or capital I) at the end? if, that could not be there.
• "Missing chrome ..." Never came across something similar. Do you have Chrome installed?
• "never any latency results", Yep, correct, it has to do with your board not having a parport. Truly a bug
• "What numbers ..." Tommy answered that already not bad values anyway. It is not paramount to get the latest % out in better latency, especially for non parport based setups. There are a number of hints and results to parameters you can add/alter in "GRUB_CMDLINE_..." line. I collected a few of these and am preparing a thread in summing the up - after getting the script cleaned out and better Meanwhile, you could dig around in the results thread and/or forum to get an idea of the multitude of all the possibilities.

Greez
chris

• pcspkr: "etc/modprobe.d/pcspkr.confI" Is there an "l" (ell or capital I) at the end? if, that could not be there.
  
  That "I" came from the forum editor when I tried to edit the post.  It trashed the whole post and I had to clean it up and I missed that.
  
• "Missing chrome ..." Never came across something similar. Do you have Chrome installed?
  
  After the error I installed Chrome but it didn't make any difference.
  
• "never any latency results", Yep, correct, it has to do with your board not having a parport. Truly a bug
  
  Ah OK.
  
• "What numbers ..." Tommy answered that already not bad values anyway. It is not paramount to get the latest % out in better latency, especially for non parport based setups. There are a number of hints and results to parameters you can add/alter in "GRUB_CMDLINE_..." line. I collected a few of these and am preparing a thread in summing the up - after getting the script cleaned out and better 
  
  I did look though some of the other post and found some more parameters to try but none of them improved the numbers.

Thanks.  This script sure beats doing the testing manually.
 

Johnny
Thx for the flowers!
If you are not getting >significant< amelioration (say > 15%) altering the "GRUB_CMDLINE_..." , stick with what you've got. Tommy usually states, that long (long in the sense of definitely considerably more than 2 hours {Tommy, please correct me, if I am wrong}). But: I guess, you know: we are working with potentially dangerous machines, are experienced enough and do what all god cnc-boys do: apply a good grain of cautiousness!
Greez
chris

Now that I have the best I've been able to get in a short run I will start a long run once the thunder storms stop

Thanks
John.