#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 jdemeyer):
Replying to [comment:10 pbruin]:
> You may want to silence these warnings as well.
I'm not convinced. This is a case where you get less memory than you
explicitly asked for. I think we should really display a warning in that
case.
> I would also suggest `allocatemem()` should print both the actual and
the maximum stack sizes with `silent=False`.
Sure.
> On a certain system that I use, this causes Sage to show up in ps or top
as using 129 gigabytes of virtual memory
I don't think that this is a problem. It's virtual and unused memory, so
it shouldn't hurt at all.
I also wouldn't want to hardcode a `parisizemax` (like in your branch, you
use 1G). If you have a machine with lots of RAM, you may want to actually
use it.
--
Ticket URL: <http://trac.sagemath.org/ticket/19883#comment:12>
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.
