John H Palmieri wrote:
> It also takes less time if you don't include plots: maybe 5 minutes for
> me instead of 8.

But sooner or later we'll have to split combinat I think, as you
mentioned, since with N threads you're just waiting faster (or rather
"in parallel") for the last part to finish, similar to building Sage
from scratch, where I meanwhile always have to wait for just SciPy
(although during the build, the number of threads actually used a couple
of times already drops down to just one or two).


Interestingly, AFAICT in (HTML) docbuilding I/O isn't an issue (perhaps
unless your disk is very very slow, or the box is in addition swapping).


-leif

> On Monday, September 5, 2016 at 10:59:19 PM UTC-7, Johan S. R. Nielsen
> wrote:
> 
>     > Regarding speed, there are two issues:
>     >
>     > 1. Building the documentation from scratch. I don't  know if we
>     can expect
>     > this to go any faster. The PDF version of the documentation is
>     3,474 pages
>     > long. No, wait, that's just the contribution from
>     references/combinat: the
>     > whole reference manual is 18,442 pages long. I can build this on
>     my machine
>     > in about 8 minutes, and this does not seem unreasonable. Am I
>     wrong about
>     > this? (It could be sped up a bit for parallel builds if the
>     largest pieces,
>     > e.g., reference/combinat, were broken into smaller pieces, but I
>     don't know
>     > how much speed increase we can hope for.)
> 
>     OK, this is good to know. It takes considerably longer on my
>     machine, so
>     there is something I'm really not doing right (possibly not having
>     parallel build enabled). I'll experiment with this.
> 
>     8 minutes from a clean build is not impressive IMHO, but perhaps it's
>     then not the most important piece of the compilation process to
>     improve..
> 
>     Best,
>     Johan


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to