Le 31/08/2016 à 00:19, Volker Braun a écrit : > On Tuesday, August 30, 2016 at 11:03:39 PM UTC+2, leif wrote: > > 48 GB claimed by *every* Sage process here > > > Its a tiny fraction of the 128TB address space. We are not talking about > used RAM here. > > which is *total* (not free!) physical RAM + total (not free) swap > space, > in bytes. > > > Really, you need to take enough address space so that any computation > that you can possibly do isn't artificially limited by the address space. > > --
Testing : x=sage.misc.memory_info.MemoryInfo().virtual_memory_limit()/1024.^3 on very different machines: 1) My own computer, 8GB RAM + swap: x: 23.1133804321289 GB 2) a machine with, 96 GB Ram + swap: x: 153.79 GB 3) My raspberry pi3 :-) 1GB, No swap : x = 0.939544677734375 GB On all these machines, sage starts gently, even if slowly (as expected) on machine 2 (uses nfs), and 3. On machine 2, sage stating process (as mesured with top) uses about 39GB (no more...) out of 153.79 available. t. -- 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.
<<attachment: tdumont.vcf>>
