On Apr 18, 2011, at 09:35 , David Kirkby wrote: > On 18 April 2011 17:18, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: >> Hello all, >> >> For all those whose installed sage-4.7.alpha2 or later (on a reasonably >> fast machine): please provide the timing of >> >> $ ./sage -t -long "devel/sage/sage/sandpiles/sandpile.py" >> >> On sage.math.washington.edu: >> Total time for all tests: 23.7 seconds >> >> But on my laptop (Gentoo Linux, Intel Core 2 Duo 2.00 GHz, gcc 4.4.3): >> Total time for all tests: 519.9 seconds >> >> It is not clear to me why there is this huge difference in timing. See >> also #10618. >> >> >> Jeroen. > > The first time I run the test, it took 47.4. Subsequent times were > much faster (25.0, 24.3 25.3 s).
This issue is just due to a "cold" application. It takes time to load all the depended-upon libraries and possibly page in a lot of application code. The second time you run the app, it's noticeably faster (this relates to a previously-discussed issue with slow startup for sage). You can get a clear picture of the startup slowness by running (something like) $ time sage < /dev/null first on a freshly booted system (to really assure that the sage bits are "cold"); and then right away repeating this command. On my system, the time to a shell prompt drops by a factor of 10 or more. Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- Like the ski resort full of girls hunting for husbands and husbands hunting for girls, the situation is not as symmetrical as it might seem. - Alan MacKay -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
