#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):
Calling mmap without MAP_NORESERVE does reserve first swap and then ram,
this is no joke and bit us with gap. Sure overcommit helps but there is a
limit to it; Really its just the final warning before the oomkiller
strikes. Overcommitting is NOT a happy place to be.
Imho the "try to allocate all memory" approach has a small chance of
messing things up badly. Sure it works almost all the time but some day
you'll succeed, sbrk almost everything into one process, and then
everybody else on the system will have a bad day. It smells of rare and
undebuggable random failures.
--
Ticket URL: <http://trac.sagemath.org/ticket/19883#comment:21>
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.
