Gap session memory limit
26 views
Skip to first unread message
mmarco
Jul 23, 2012, 4:49:40 AM7/23/12
to sage-devel
Right now the gap session used by sage is started with a memory limit
set by -o 9999G, which, in practice, means that there is no memory
limit.
The problem is that when it runs a computation that needs more memory
than what the system has available, it consumes it all, since the OS
decides to kill the process. When that happens, all the sage objects
that point to gap objects are orphaned, and hence, not working
anymore.
So i would propose to change the default option for gap in such a way
that the allocated memory deppends on the available memory on the
system (say, a 75% of the total memory). That way, when a gap
computation takes too much memory, gap itself would stop it, returning
a MemoryError, but without killing the session.
Thoughts?
set by -o 9999G, which, in practice, means that there is no memory
limit.
The problem is that when it runs a computation that needs more memory
than what the system has available, it consumes it all, since the OS
decides to kill the process. When that happens, all the sage objects
that point to gap objects are orphaned, and hence, not working
anymore.
So i would propose to change the default option for gap in such a way
that the allocated memory deppends on the available memory on the
system (say, a 75% of the total memory). That way, when a gap
computation takes too much memory, gap itself would stop it, returning
a MemoryError, but without killing the session.
Thoughts?
Reply all
Reply to author
Forward
0 new messages