On Fri, Mar 19, 2010 at 12:49 PM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > For your information, > > $ make testlong > > ends with: > > sage -t -long "devel/sage/sage/symbolic/__init__.py" > [0.3 s] > sage -t -long "devel/sage/sage/symbolic/constants_c.pyx" > [11.9 s] > sage -t -long "devel/sage/sage/symbolic/callable.py" > [9.8 s] > > ---------------------------------------------------------------------- > All tests passed! > Total time for all tests: 41636.5 seconds > > That was on a machine bought for about $75 on eBay. On 't2' I'd expect the > tests to take quite a bit longer. Funny really, how a machine worth around > $30,000 can be outperformed by one costing less than $100, simply because > the T5240 (t2) is so ill-suited for Sage development.
That's an unfair comparison. If you run "make ptestlong" on t2 with 32 threads, with no other load on the machine, it will finish in about 1 to 1.5 hours, much less than the 11 hours or so listed above. The point of multi-cpu machines is not that one of their cpus is particularly powerful, but that you use as many of them as possible. I'm not saying that t2 is a dream machine for Sage development, but that it's what we have and there are ways of using it more efficiently than running "make testlong" (or for that matter running 100 threads). Best, Alex -- Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne -- Australia -- http://www.ms.unimelb.edu.au/~aghitza/ -- 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 To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
