#2695: ensure that we have sufficient amounts of RAM to build Sage
-------------------------------+--------------------------------------------
Reporter: mabshoff | Owner: mabshoff
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.10
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by leif):
Replying to [comment:10 jdemeyer]:
> Replying to [comment:8 leif]:
> > Nope; I actually wanted to add "not that long ago"... Mid or late
2011 IIRC (last time I recall having tested that; i.e., probably even past
that time).
> I don't believe you, the Heegner tests exist longer than that and always
required around 2GB of memory.
I'm especially sure about the tests in `schemes/elliptic_curves/`, since
these used to be the record holders, as mentioned. :-)
This is just one example of a couple of doctests where PARI tries to
'''allocate''' a huge amount of memory, but actually '''uses''' only a
fraction of it. (You might have to set up enough swap space to run these
tests, but you'll usually not experience swapping even with just 512 MB
RAM, say.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/2695#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 http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
