On May 29, 2012, at 00:41 , Jonathan Bober wrote: > see http://trac.sagemath.org/sage_trac/ticket/13057 > > This seems to be a bad regression. On reasonable machines it can take > 5 seconds to get the docstring of an object by using '?'. Does anyone > have any idea what happened? I don't see any changes to > sage/misc/sagedoc.py or sage/misc/sageinspect.py in the last few > months that seem like they would cause this.
I'm not sure what the cause is, but I do see this. On my 2.93 GHz Dual 6-core Xeon system, I started each of the following versions from scratch, and ran "gcd?", with the indicated times 4.7.2: ~1 second 4.8: ~2-3 seconds 5.0: ~6-7 seconds There was nothing else going on at the time (except a "doc build" of 5.1b1, which is hardly a cpu/disk hog). Note that, for some reason, just doing "gcd?" launches GAP in the background, which may account for some of the delay; since GAP is launched in each case above, that only makes sense if something has changed in the Sage/GAP interaction (or in GAP itself, but each of the above uses 4.4.12.p6, so, ...). Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- I'm beginning to like the cut of his jibberish. ----------- -- 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
