Hi leif,
> On 3 Jun., 15:20, Florent Hivert <[email protected]> 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)?
If you look at my new patch on trac I don't import sage.all though I search
into it. Here are the result for a single file:
Without:
sage -docbuild reference html 11,63s user 0,94s system 98% cpu 12,799 total
sage -docbuild reference html 11,70s user 0,90s system 98% cpu 12,776 total
sage -docbuild reference html 11,82s user 0,84s system 98% cpu 12,834 total
With:
sage -docbuild reference html 11,67s user 0,96s system 98% cpu 12,815 total
sage -docbuild reference html 11,59s user 0,96s system 98% cpu 12,679 total
sage -docbuild reference html 11,78s user 0,87s system 98% cpu 12,793 total
I see nothing very significative... Note that the things worked since I got
the message:
Searching sage.combinat.partition.Partitions from sage.combinat.integer_list
WARNING: undefined symbol :mod:`sage.combinat.partition.Partitions` in module
sage.combinat.integer_list
Cheers,
Florent
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
