#19883: Let PARI handle its own stack
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-7.0
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: Jeroen Demeyer | Work issues:
Report Upstream: Reported | Commit:
upstream. No feedback yet. | 435a4fe79fb3b2d7a652c4d512bc6531c4762ab3
Branch: | Stopgaps:
u/jdemeyer/let_pari_handle_its_own_stack|
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by vbraun):
How is Pari implementing this? In GAP its mmap **without** MAP_NORESERVE,
so even if its just virtual memory it reserves swap. And if you do it
often (parallel doctesting comes to mind) your swap is used up and virtual
allocations suddenly are forced into ram.
There is sage.misc.memory_info to detect ram / swap.
Gap uses it in sage.interfaces.gap.get_gap_memory_pool_size
--
Ticket URL: <http://trac.sagemath.org/ticket/19883#comment:15>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
