On Mon, Feb 13, 2012 at 6:16 AM, Jason Grout <jason-s...@creativetrax.com> wrote: > On 2/13/12 8:05 AM, Keshav Kini wrote: >> >> It seems to me that something is wrong again. Sagenb has been thinking >> about [factorial(x) for x in range(10)] for several minutes. > > > This is in the error logs: > > exceptions.RuntimeError: Pexpect: pty.fork() failed: [Errno 12] > Cannot allocate memory > > top shows that there is about 1.8G of RAM available. That's a problem. > > William: it seems like you're up. Do you want to take a look at it?
This is probably caused by somebody doing real work on that machine: 17831 stromber 35 15 22.4g 21g 38m S 0 17.7 4211:30 python 28176 stromber 35 15 15.1g 14g 38m S 0 11.7 2092:33 python 3359 sagenb 35 15 2205m 1.4g 25m S 19 1.1 706:52.97 python 3352 sagenb 20 0 1215m 591m 24m S 0 0.5 0:52.17 python I've increased the vm.overcommit_ratio some, which will allow for more processes to get swapped out, which should help. I had vm.overcommit_ratio pretty conservatively configured. -- William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
