Hi, On 29/06/21 at 23:21 -0400, Louis-Philippe Véronneau wrote: > Felix asked me to report the performance data for the lintian testsuite > I'm getting on my new desktop computer. > > Let me first say I'm a very casual contributor to Lintian and I'm > certainly not in a position to judge if the testsuite takes too much > time to run or is too extensive by default. Take this as additional data > to make informed decisions :) > > On my previous desktop computer (AMD FX-8530, 8GB DDR3 RAM, SATA SSD), > running the testsuite used to take up to 15mins. > > Now with the new PC (AMD Ryzen 5900x, 64GB DDR4 RAM, M.2 NVME SSD), it > takes less than 3 minutes. This is the result of running > `private/runtests` from a newly created git clone of the current master > branch: > > ----------------------------------------------------------------------- > All tests successful. > Files=1306, Tests=59485, 178 wallclock secs ( 6.85 usr 2.34 sys + > 3356.34 cusr 422.52 csys = 3788.05 CPU) > Result: PASS > > The test suite ran for 2 minutes and 59 seconds. > ----------------------------------------------------------------------- > > Then again, that's a brand new machine running top of the line > consumer-grade hardware, with a beefy cooler :)
I can confirm those numbers (less than 3 minutes for a full run): > Files=1516, Tests=64173, 169 wallclock secs (13.08 usr 7.47 sys + 9158.16 > cusr 1997.99 csys = 11176.70 CPU) > Result: PASS > > The test suite ran for 2 minutes and 50 seconds. > > 9172.52user 2005.72system 2:50.09elapsed 6571%CPU (0avgtext+0avgdata > 447804maxresident)k > 0inputs+0outputs (6584major+260243917minor)pagefaults 0swaps Note that tests from private/runtests run in parallel since commit da82572b29 (December 2020), which explains the difference with the numbers reported earlier in that bug. I suppose that the salsa VM only uses a limited number of cores, which would explain why it's still slow there. Lucas
