On Thursday, December 13, 2012 10:06:47 PM UTC, Dima Pasechnik wrote: > it might be GAP to blame, in part, as GAP reserves an amount of swap > sort of proportional to available RAM.
Right now it basically eats all available swap, this is going to be fixed in #13211 > Now imagine you run 50 Sage > sessions, each with an instance of GAP reserving a chunk of swap. Then the GAP pool will become smaller for each subsequent session as 1/10th of the remaining swap (the default choice) gets less and less. -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/-CxzWgqATp8J. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
