William Stein wrote:
Does anybody know how much RAM is required to build Sage these days.
  With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB
RAM results in failure (see below).  Of course, I'm not using swap,
and of course with swap you can do anything if you're willing to wait.
  That said, it would be very useful to have some sort of statement
about required RAM, like we now have for disk space: "Make sure you
have the dependencies and 5 GB of free disk space."

For the record, I just built Sage 6.2 from scratch on a 32-bit (x86) Linux box with just 2 GB RAM (but of course swap enabled), with FSF GCC 4.8.2* and '-O3', using *three* jobs/threads (although it's just a single-core), with GNOME running.

While compilation used slightly more than half of the RAM (e.g. when building Singular), docbuilding first took about one third (virtual), but the second pass of building the reference manual about twice that much, peak about 1.5 GB (according to 'top' and the sysload applet).

So you probably had lots of other processes consuming memory (not necessarily running, which is another argument for enabling swap), and/or probably /tmp set up as a ramdisk.


[ptestlong still in progress; this time I did /not/ forget to delete previous timing data in ~/.sage/ in order to *not* run all greedy tests at the same time, i.e., at the beginning, because doing so would just take longer due to heavy swapping.]


-leif

___________
* Newer versions of GCC, especially g++, and in particular with '-O3', are said to use less memory than previous versions did, which from my experience seems to be true.

--
() The ASCII Ribbon Campaign
/\   Help Cure HTML E-Mail

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to