Hallo Kent, Please let it run overnight, my poor old Dell wanted to go to bed sometime after midnight and gave some horrible results next morning (been sleeping at the wheel, obviously). Although it looked quite happy for the first hour or so.
The other thing to watch out for is frequency throttling when not busy. It bugs your latency straight away. https://www.osadl.org/Single-View.111+M52601a5fd69.0.html And the last thing: Some kernels behave better than others on certain CPU's, and that is probably the nastiest problem of the lot. But this is life. Cheers, j. On Sat, Sep 15, 2012 at 5:55 PM, Kent A. Reed <kentallanr...@gmail.com>wrote: > Gentle persons: > > As a brief summary... > > I reset the BIOS on my ASUS AT5NM10-I to nearly default settings, > including enabled Hyperthreading. I did leave audio processing disabled. > > I built and ran the OSADL cycletest (hint: first install the libnuma1 > and libnuma-dev packages) with essentially the settings they used to > generate latency histograms except I ran it for 30m to get a feel for > the test. I get essentially the same results they did. The four threads > (2cores+hyperthreading) came in at max latencies 42us, 61us, 61us, 53us. > > I then ran our LinuxCNC latency-test with a 200us base thread for 30m. > Two copies of glxgears were running to give a little loading. I actually > got somewhat better max latencies: ca 35us on base and servo threads. > > Conclusions: > > 1) the board is probably doing as well as it can with RT PREEMPT and is > probably useful with hardware pulse-generators. > > 2) the latency data on the OSADL website are approximately useful for > preliminary assessments. In addition to the systems I compared with my > efforts, there are several systems under test there that (only) > approximate the boards Charles has tested. The OSADL latencies are > within a factor of 2 of Charles' results. > > Aside: different sites (including our own) use subtly different > definitions of latency. It would be useful for someone better versed > than I am to illuminate this topic. > > Regards, > Kent > > > > ------------------------------------------------------------------------------ > How fast is your code? > 3 out of 4 devs don\\\'t know how their code performs in production. > Find out how slow your code is with AppDynamics Lite. > http://ad.doubleclick.net/clk;262219672;13503038;z? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
