> How does this sound. > > 1) We add an environment variable SAGE_ATLAS_THREADS > 2) If unset, then the behavior is unchanged, so we build an unthreaded > ATLAS. 3) If set to "auto": > > $ export SAGE_ATLAS_THREADS=auto > > then we let ATLAS automatically determine the number of threads. (I think > that is what ATLAS determines as the number of processors on your system. > IIRC, on 't2.math' this was 128). > > 4) If set to an integer N, > > $ export SAGE_ATLAS_THREADS=8 > > we use N (in this case 8) threads.
Hi, somehow I get the feeling the number of environment variables in Sage is increasing on an exponential rate. I'd much rather not have some ATLAS specific environment variable. Instead - if we need a variable - I'd have SAGE_NUM_CORES or something. William convinced me the other day that it would be better to build with multicore support by default (since that's the future anyway) instead of only if some obscure variable is set. I'm sure this would require more work but might be a worthwhile activity. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://www.informatik.uni-bremen.de/~malb _jab: martinralbre...@jabber.ccc.de -- 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
