On 2016-09-19 14:04, Jonathan Bober wrote:

That doesn't really solve the problem, which I phrased poorly. The machine has an (antiquated) setup where, when a process requests X bytes of memory, the kernel reserves X bytes of physical memory for it.

## Advertising

`Well, in that case you would indeed "lose" 1/4 of your physical memory`

`using the defaults that Sage uses for the PARI virtual stack. If you are`

`unwilling to change your OS settings, then you can still manually change`

`the PARi stack size with`

from sage.libs.pari.all import pari pari.allocatemem(4*10^6, 4*10^6)

Anyway, where exactly is this allocation coming from? Is it a default PARI setting, or does it come from the way that Sage uses PARI?

It is because of the way how Sage uses PARI.

I mean, to whom should I address my "hate mail"? :)

That would be me... Jeroen.

`PS: The Sage <-> GAP interface has exactly the same problem, but with a`

`smaller default memory allocation.`

-- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.