On Thu, Jan 21, 2010 at 9:10 AM, Robert Miller <r...@rlmiller.org> wrote: > William wrote: >> It's possible he didn't set the DOT_SAGE environment variable to >> something in /scratch, which will impact timings hugely (at least >> until somebody rewrites Sage temp file code in misc/misc.py to use the >> standard tempfile module). > > DOT_SAGE was set to /scratch/rlm/.sage when I ran these tests.
If the problem really is the filesystem, then maybe /scratch is way too slow. Can you try setting DOT_SAGE to something in /tmp or /space, since /tmp could be far better than /scratch for large numbers of accesses. > > David Joyner wrote: >> If Robert's minimum distance procedure for binary codes could >> be extended to the non-binary case, that might solve the problem. Comments >> on this Robert? > > Don't hold your breath. > > Those timings were the results of doing "sage -tp 20" or some similar > number of processes on sage.math. That is the situation in which we > want to shorten the runtime of doctests. > > > > -- > Robert L. Miller > http://www.rlmiller.org/ > > -- > 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 > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org
-- 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
