On 07/17/10 01:07 PM, William Stein wrote:
On Sat, Jul 17, 2010 at 2:03 PM, Dr. David Kirkby
<david.kir...@onetel.net> wrote:
On 07/17/10 12:32 PM, William Stein wrote:
On Sat, Jul 17, 2010 at 1:16 PM, Robert Miller<rlmills...@gmail.com>
wrote:
With the rest of the packages, we just do
export MAKE="make -j6"
to enable parallel building. Why don't we just use this in atlas as
well? Why do we need to make a special case?
I think the OP was suggesting building ATLAS so that when it is later
run it can use multiple cores.
The above MAKE option merely impacts build time, which is an orthogonal
problem.
I'm -1 to adding too many environment variables that impact the built
Sage, because it makes testing sage much, much more difficult, since
it leads to a combinatorial explosion in the number of different sage
versions we should test.
-- William
So what do you suggest with ATLAS?
* Always build with no threading, as is done now?
No.
* Always build so that ATLAS choses the number of threads automatically?
Yes.
OK, though you might have to accept that is less safe.
However, with SAGE_FAT_BINARY set, i.e., when making a binary for
distribution, maybe then we have to build without threading support.
I don't' see why, since the number of threads is determined automatically. I
*assume* that means at runtime, though I'm not 100% sure. I would need to ask
Clint.
Give just about modern machines are at least dual core, perhaps having two
threads is better than 1 even if SAGE_FAT_BINARY is set. What do you think?
-- William
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
