I tried building rust in a VM with 1GB of memory and it seems only zswap works. With zram-only solution without any real swap I was not able to compile rust at all. The compiler generated out-of-memory exception with zram configured to take 30-70% of memory. With zswap enabled, zswap.max_pool_percent=70 and the real swap of 2.5 GB the compilation time for the latest tip was about 2 hours. This is on Mac Air and Linux inside VirtualBox.
On 5 June 2014 20:46, Ian Daniher <[email protected]> wrote: > zram is a great suggestion, thanks! I'll give it a shot. > — > From My Tiny Glowing Screen > > > On Thu, Jun 5, 2014 at 2:25 PM, Igor Bukanov <[email protected]> wrote: >> >> Have you considered to use zram? Typically the compression for >> compiler memory is over a factor of 3 so that can be an option as the >> performance degradation under swapping could be tolerable. A similar >> option is to enable zswap, but as the max compression with it is >> effectively limited by factor of 2, it may not be enough to avoid >> swapping. >> >> On 5 June 2014 20:13, Ian Daniher <[email protected]> wrote: >> > 1GB is close-ish to the 1.4GB last reported (over a month ago!) by >> > http://huonw.github.io/isrustfastyet/mem/. >> > >> > Are there any workarounds to push the compilation memory down? I'm also >> > exploring distcc, but IRFY has a bit of semantic ambiguity as to whether >> > or >> > not it's 1.4GB simultaneous or net total. >> > >> > Thanks! >> > -- >> > Ian >> > >> > _______________________________________________ >> > Rust-dev mailing list >> > [email protected] >> > https://mail.mozilla.org/listinfo/rust-dev >> > > > _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
