#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. | 5bc6f271aa21be3f54b12322f7dde9b3d5b04fe9
Branch: | Stopgaps:
u/jdemeyer/let_pari_handle_its_own_stack|
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by pbruin):
I'm not sure what to think about the strategy to set the maximum PARI
stack size to 1/4 of the maximum amount of memory that `malloc()` can
allocate. On a certain system that I use, this causes Sage to show up in
`ps` or `top` as using 129 gigabytes of virtual memory (and
`pari.stackmax()` returns exactly 128 gigabytes). Of course this is
harmless as long as the memory isn't actually used, but it looks/feels
somewhat absurd.
--
Ticket URL: <http://trac.sagemath.org/ticket/19883#comment:11>
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.
