https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251886
--- Comment #12 from Mark Millard <marklmi26-f...@yahoo.com> --- (In reply to igor.polovykh from comment #11) I do not know if you have ZFS or other sources of possibly significant memory use, depending on ZFS tuning. But I on occasion do -j4 buildworld's on machines with 16 GiByte, 12 GiByte, 8 GiByte, 4 GiByte, and even 2 GiByte --but with the types of tuning that I reported. This is over a variety of archtiectures: powerpc64 (12 GiByte these days), armv7 (2 GiByte), aarch64 (16/8/4 GiByte), each with 4 cores. (My amd64 context has lots more RAM and hardware threads --and so is not comparable.) All these are UFS based contexts, all SSD based (many using USB3 SSDs), SSDs that seem to perform nicely for the purpose. I also avoid tmpfs or other such to avoid the memory use competing with the compiler and linker instances. I also have used ( in /etc/make.conf ): LDFLAGS.lld+= -Wl,--no-threads to limit the llvm linker's multi-threading (for its memory use consequences). So linking may take longer. I have done a "13" buildworld on a 1 GiByte aarch64, but not with -j4 . If I remember right it was -j2 . This is the only context to use significant swap/paging space as I remember, significant enough that -j3 likely would not have worked. (I normally keep the swap space sized somewhat below where booting would start to complain about it being too much without other tuning.) Another point is that these machine are not running X11 or other such: serial console and console-like ssh use. Strongly biased to the resources being available to the builds overall. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
