From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: btop fails to compile
Date: Mon, 5 Dec 2022 01:30:22 -0500 [thread overview]
Message-ID: <Y42P/quHwAB9kWq/@waltdnes.org> (raw)
In-Reply-To: <6e4bdde2ba014b589087e2cf4d7027c6@jk-foto.design>
On Wed, Nov 30, 2022 at 01:50:02PM +0100, Jochen Kirchner wrote
> this is my make.conf: (its a web - and mail server)
>
> MAKEOPTS="-j17 -l17"
Ouch!!! How much ram do you have on that machine? The Gentoo install
handbook has a dire warning at...
https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#MAKEOPTS
...that you need approx 2 gigabytes free ram for each increment in
"MAKEOPTS".
> * Warning
> Using a large number of jobs can significantly impact memory
> consumption. A good recommendation is to have at least 2 GiB of RAM
> for every job specified (so, e.g. -j6 requires at least 12 GiB). To
> avoid running out of memory, lower the number of jobs to fit the
> available memory.
If you have a fancy-schmancy "desktop environment" allow another 3 or
4 Gigs, especially if you're simultaneously running Chrome or
calculating large spreadsheets or processing large documents. For
"MAKEOPTS=-j17" you'll need at least 36-to-40 gigabytes.
--
I've seen things, you people wouldn't believe; Gopher, Netscape with
frames, the first Browser Wars. Searching for pages with AltaVista,
pop-up windows self-replicating, trying to uninstall RealPlayer. All
those moments, will be lost in time like tears in rain... time to die.
next prev parent reply other threads:[~2022-12-05 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 9:32 [gentoo-user] btop fails to compile Jochen Kirchner
2022-11-30 11:31 ` [gentoo-user] " Nuno Silva
2022-11-30 11:45 ` Dale
2022-11-30 12:50 ` Jochen Kirchner
2022-12-05 6:30 ` Walter Dnes [this message]
2022-12-05 8:21 ` Peter Humphrey
2022-12-14 7:14 ` Jochen Kirchner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y42P/quHwAB9kWq/@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox