On Sat, Aug 2, 2014 at 2:23 PM, H. Peter Anvin <h...@zytor.com> wrote: > It would be nice to automate running a T-test on it.
I'll see if I can do something like that. Using the t statistic seems like overkill here, though -- timing_test_64 runs millions of iterations, so even if I batch them, I'll end up with n ~ 1000 (or even larger), at which point plain old Gaussians should be fine. --Andy > > On August 2, 2014 2:14:50 PM PDT, Andy Lutomirski <l...@amacapital.net> wrote: >>On Fri, Aug 1, 2014 at 3:13 PM, H. Peter Anvin <h...@zytor.com> wrote: >>> On 08/01/2014 03:11 PM, Denys Vlasenko wrote: >>>>> >>>>> Could you please try to see if there is a measurable change in the >>>>> latency of a trivial syscall? >>>> >>>> Will do. >>>> Something along the lines of "how long does it take to execute two >>>> gazillions of getppid()?" >>>> >>> >>> Something like that, yes, but you have to run enough data points so >>you >>> can determine if the difference is statistically significant or just >>noise. >> >>Denys, if you want to avoid five minutes of programming, you can build >>this: >> >>https://gitorious.org/linux-test-utils/linux-clock-tests/ >> >>and run timing_test_64 10 getpid >> >>It doesn't do real statistics, but it seems to get quite stable >>results. >> >>--Andy > > -- > Sent from my mobile phone. Please pardon brevity and lack of formatting. -- Andy Lutomirski AMA Capital Management, LLC -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
