#9865: Unable to start singular because the command 'Singular -t --ticks-per-sec
1000' failed
-----------------------+----------------------------------------------------
   Reporter:  mpatel   |       Owner:  mvngu   
       Type:  defect   |      Status:  new     
   Priority:  blocker  |   Milestone:  sage-4.6
  Component:  doctest  |    Keywords:          
     Author:           |    Upstream:  N/A     
   Reviewer:           |      Merged:          
Work_issues:           |  
-----------------------+----------------------------------------------------

Comment(by leif):

 Replying to [comment:5 ddrake]:
 > Replying to [comment:4 cschwan]:
 > > I remember having the same failure in free_module.py and I think its
 most likely caused by having not sufficient memory - everytime I run
 free_module.py's my system (i686 + 1GB RAM + 512 MB swap) is heavily using
 swap.
 >
 > Interesting. On the Arch VM where I was seeing the same problem,
 increasing the RAM allocated to the VM from 1152 MB up to 1768 MB seems to
 fix the problem. (Using 4.5.3.alpha2.) But there are still questions: why
 do the tests pass when run in Sage normally? Does the doctest framework
 really take 600+ MB of memory? And why exactly does Singular fail to start
 -- is it just unable to allocate enough memory? If so, can we get a better
 error message? These tests seem to work on non-VMs with less memory -- or
 do they? Why is that?

 I've successfully built and {{{p}}}test{{{long}}}ed recent versions of
 Sage on e.g.:
  * Single-core (no HT either) with only 768 MB (and GUI running), and I
 believe half of that would not cause swapping. (IIRC built with 2 jobs,
 tested with only one thread.)
  * Quad-core (no HT) with 8 GB: Built with 32 jobs, {{{ptestlong}}} with
 64(!) threads without swapping. (I then only further tried {{{ptestlong}}}
 with 128 threads, which as expected caused massive swapping s.t. almost
 all tests timed out.)

 I recently examined the memory consumption of testing files in
 {{{sage/schemes/elliptic_curves}}} since these were said to be the record
 holders. The "winner" of these was {{{sha_tate.py}}} with a peak usage
 (just that process) of 226 MB.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9865#comment:7>
Sage <http://www.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.

Reply via email to