#13880: Respect ulimit -v for GAP memory pool size
--------------------------------+-------------------------------------------
       Reporter:  vbraun        |         Owner:  jason       
           Type:  defect        |        Status:  needs_review
       Priority:  major         |     Milestone:  sage-5.6    
      Component:  misc          |    Resolution:              
       Keywords:                |   Work issues:              
Report Upstream:  N/A           |     Reviewers:              
        Authors:  Volker Braun  |     Merged in:              
   Dependencies:                |      Stopgaps:              
--------------------------------+-------------------------------------------

Comment (by leif):

 Replying to [comment:4 vbraun]:
 > Replying to [comment:3 leif]:
 > > Why `available_swap() in ZZ`?
 >
 > To test that it returns an integer as promised in the docstring.

 Not that obvious, to me at least... ;-)

 Still wonder whether we shouldn't also test that the result is actually
 non-negative.

 [[BR]]

 > I've added a manual 2GB limit for the rare case of 32-bit machines with
 >> 2GB ram.

 Ok.  (The more common case -- which I meant -- is having >> 2 GB ''swap
 space'', which is handled now as well.)

 [[BR]]

 Slightly related (`memory_info.py` probably deserved its own ticket):

 `available_ram()` should probably have an optional boolean parameter to
 not just return the amount of ''free'' memory ("`MemFree`"), as this can
 often be pretty close to zero, due to buffering and especially caching.
 (I.e., the amount of "available" RAM, allocatable by a process without
 running out of [physical] memory, might in fact be much larger, regardless
 of whether swap space is available or not.)

 As is, although its docstring contains "free" in parentheses, the term
 "available RAM" is IMHO potentially misleading.

 W.r.t. GAP, I think it may currently "run out of memory" simply because
 [there's no or not enough swap space ''and''] most (or at least much) of
 the physical memory is eaten up by just caches.

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