On 3 Jun., 15:20, Florent Hivert <florent.hiv...@univ-rouen.fr> wrote: > On Wed, Jun 02, 2010 at 05:34:06PM -0700, leif wrote: > > Any measures of the slow down to Sphinx? > > I don't think it would be very measurable: Here is a comparison after issuing > # touch *.py && sage -b && time sage -docbuild reference html > > without: > sage -docbuild reference html 46,81s user 1,06s system 98% cpu 48,604 total > sage -docbuild reference html 46,61s user 1,10s system 98% cpu 48,279 total > > with: > sage -docbuild reference html 46,19s user 1,25s system 96% cpu 49,228 total > sage -docbuild reference html 46,37s user 1,11s system 98% cpu 48,182 total
Does not really address my question. Think of a single file, what's the price/latency of importing sage.all to resolve not fully qualified targets (perhaps just a single one)? -Leif -- 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
