#13880: Respect ulimit -v for GAP memory pool size
--------------------------------+-------------------------------------------
Reporter: vbraun | Owner: jason
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-5.6
Component: misc | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by dimpase):
Replying to [comment:27 vbraun]:
> `/proc/meminfo` doesn't exclude reserved yet unused swap in the
!SwapFree field.
>
>
> I've renamed the (private) dict key to `free_swap`. In any case thats
not visible to the user.
This is not enough.
I still get
{{{
File "/usr/local/src/sage/sage-5.6.beta2/devel/sage-
main/sage/misc/memory_info.py", line 122:
sage: mem.virtual_memory_limit() > 0
Expected:
True
Got:
False
}}}
virtual_memory_limit() as implemented is too conservative, I think.
Indeed:
{{{
sage: from sage.misc.memory_info import MemoryInfo
sage: mem = MemoryInfo()
sage: mem.av
mem.available_ram mem.available_swap
sage: mem.available_swap()
-5123952640
sage: mem.available_ram()
1262751744
sage: mem.virtual_memory_limit()
-3861200896
}}}
unless you will allow virtual_memory_limit() be negative, too, but this is
IMHO even weirder...
Shouldn't an implementation respect the overcommitting settings somehow?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13880#comment:28>
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.
