On Tuesday, August 30, 2016 at 8:26:29 PM UTC+2, leif wrote: > > IMHO horrible (as *each* Sage subprocess is claiming that amount of > memory, here usually ~28 to 50+ GB IIRC, as it depends on the physical > memory installed) and dangerous, as this makes the usage of 'ulimit -v' > nearly impossible
ulimit -v is useless anyways > and in practice requires to allow vm-overcommit. In the default mode (overcommit_memory==0) calls to mmap with MAP_NORESERVE are not checked, so you don't have to do anything special. Really, restricting virtual memory on a 64-bit system is only for specialist applications. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
