#6283: [with patches, needs review] Make it so NUM_THREADS is set intelligently
instead of idiotically in makefile so doing "make ptest" or "make
ptestlong" doesn't kill some computers
---------------------+------------------------------------------------------
Reporter: was | Owner: jhpalmieri
Type: defect | Status: assigned
Priority: major | Milestone: sage-4.1.2
Component: doctest | Keywords:
Reviewer: | Author: John Palmieri
Merged: |
---------------------+------------------------------------------------------
Comment(by jhpalmieri):
Replying to [comment:3 ddrake]:
> Hrm, I just checked on T2, and multiprocessing.cpu_count() returns 128
on that machine, which perhaps is not ideal. The whole issue of
cpus/cores/threads is really complicated -- see our own drkirkby. I think
we can ignore this issue for the moment, since Sage doesn't even really
build on T2.
I'm happy to ignore this. If it returns the "wrong" number, that seems
like a bug in Python.
I don't have access to many different kinds of machines. Should we ask
people on sage-devel to test {{{multiprocessing.cpu_count()}}}?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6283#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
