#7011: fiddle with the number of threads automatically used for parallel testing
-------------------------+--------------------------------------------------
Reporter: ddrake | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone:
Component: doctest | Keywords:
Reviewer: | Author:
Merged: |
-------------------------+--------------------------------------------------
At #6283, we changed the parallel testing framework so that it
automatically uses all the cores/threads available, but perhaps this is
not the best solution.
Dave says ([comment:9:ticket:6283]) "I would have personally not allowed
the default to exceed 8", so maybe we can incorporate his limit in a way
that still lets ordinary multicore computers be well-used:
* NUM_THREADS defaults to 0, which is now interpreted in the sage-ptest
script as min(cpu_count(), 8) -- so the default doesn't exceed 8, as Dave
suggested.
* if NUM_THREADS is -1, it just uses cpu_count().
On sage-devel, I suggested that a solution that works really well for 99+%
of people is a good one -- and since most "regular" machines on which Sage
is doctested have 8 or fewer cores, this still works fine for them, and
with the above suggestion, people won't bring sage.math or t2.math to
their knees.
Thoughts?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7011>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---
