On Oct 26, 2008, at 2:15 PM, Georg S. Weber wrote: > > Hi, > > I know now how to change the code so that when we had before: > > sage: time for i in range(10^4): float(1)/2 > CPU times: user 17.72 s, sys: 13.44 s, total: 31.16 s > Wall time: 31.20 s > > then after the changes we get: > > sage: time for i in range(10^4): float(1)/2 > CPU times: user 0.37 s, sys: 0.00 s, total: 0.37 s > Wall time: 0.37 s > > which is quite impressive, I think (the sys time is used up only by > these insanely many calls to "stat")! > > Essentially all one has to do is not to call "sys.exc_info()" in > "_record_exception" (file: sage/structure/coerce.pyx) unless you > really want to do so. But to fix that nicely (e.g. not leaving a > broken doctest) will take me another evening or two.
Thanks for tracking this down. Just out of curiosity, how does one decide if one "really wants to." Ideally one could snapshot the traceback without touching every file involved. BTW, using RDF rather than float will be 10x faster in this case even after your speedup. sage: sage: time for i in range(10^4): RDF(1)/2 CPU times: user 0.03 s, sys: 0.00 s, total: 0.03 s Wall time: 0.03 s - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
