#11959: build spkgs in parallel by default
---------------------------+------------------------------------------------
   Reporter:  jhpalmieri   |          Owner:  GeorgSWeber                       
     
       Type:  enhancement  |         Status:  needs_review                      
     
   Priority:  minor        |      Milestone:  sage-4.7.3                        
     
  Component:  build        |       Keywords:  SAGE_PARALLEL_SPKG_BUILD MAKE -j 
--jobs
Work_issues:               |       Upstream:  N/A                               
     
   Reviewer:               |         Author:  John Palmieri                     
     
     Merged:               |   Dependencies:                                    
     
---------------------------+------------------------------------------------

Comment(by leif):

 W.r.t. the Sage Installation Guide:

 `export MAKE='make -jNUM'` is not ''"a common setting of `MAKE`"'', but a
 shell command to set `MAKE`; `'make -jNUM'` is the setting.  (This has
 been in before.)

 `s/`''won't need to use''`/`''won't need to set''`/` (dito)

 `s/`''can speed up the process''`/`''can significantly speed up the
 process''`/`

 I'd omit ''"(Not all packages support this, but the ones for which this
 could be problematic should automatically disable it.)"'' since this is
 pretty irrelevant (or confusing); or rephrase it to say that a few
 packages do not support building them with multiple jobs and hence are
 built sequentially, although in parallel ''with other packages''.

 In the warning, substitute ''one-processor'' by ''single-core CPU'' or
 ''single-core machine''.  I'd also mention the platform (or operating
 system) to which this apparently applies; in my experience it is a non-
 issue on Linux.  Attempting to build Sage with probably too many jobs
 should in general not hurt; one can simply reduce the number of jobs upon
 build errors and restart, or more precisely continue, the build afterwards
 by again typing `make`.


 Similar what I've said w.r.t. `README.txt` applies to the Installation
 Guide.

 Also we should somehow mention potential problems with ATLAS there, and
 perhaps what I said about self-tuning packages in general (on sage-devel).
 (Again, if ATLAS failed to build -- often just due to too high system load
 -- one can simply type `make` again, perhaps multiple times, since there
 are usually less packages left to build when `make` finally exits.  If we
 haven't already, we should also mention that CPU throttling aka power-
 saving mode should be turned off; "on-demand" in contrast should be ok,
 i.e., provided it works properly. [I don't know whether that's in the
 `README.txt`; I think it is important enough that it should be there,
 too.])

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11959#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to