From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Smith <paul@mad-scientist.net>
Cc: Fiodar Stryzhniou <fedor_qd@mail.ru>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Out of memory while building GCC 12.1.0
Date: Fri, 10 Jun 2022 12:15:40 -0500 [thread overview]
Message-ID: <20220610171540.GT25951@gate.crashing.org> (raw)
In-Reply-To: <fd0a20e91b4d25ce95f5f18ca21c3302cdf55e96.camel@mad-scientist.net>
On Fri, Jun 10, 2022 at 01:09:30PM -0400, Paul Smith wrote:
> On Fri, 2022-06-10 at 10:56 -0500, Segher Boessenkool wrote:
> > The load average is only computed every 5s, so if you have a faster
> > machine it can bring your system to its knees in that time already,
> > by starting thousands of tasks.
>
> This is no longer true as of GNU make 3.81 (released in 2006). GNU
> make artificially adjusts the load average based on the number of jobs
> started in the last second, to avoid this issue.
I have seen it happen with GNU make 3.82. The newer heuristic is
better, sure, but it is still a heuristic based on flawed data, so it
can never be perfectly good.
> In the next release of GNU make a different method, based on /proc, is
> used for Linux specifically which should result in even better behavior
> there.
Great to hear that! So in a year or ten people can use this safely :-)
Segher
prev parent reply other threads:[~2022-06-10 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 11:55 Fiodar Stryzhniou
2022-06-10 12:14 ` Xi Ruoyao
2022-06-10 12:18 ` Jonathan Wakely
2022-06-10 12:29 ` Fiodar Stryzhniou
2022-06-10 12:42 ` Jonathan Wakely
2022-06-10 15:06 ` Fiodar Stryzhniou
2022-06-10 14:42 ` Paul Smith
2022-06-10 15:56 ` Segher Boessenkool
2022-06-10 17:04 ` Fiodar Stryzhniou
2022-06-10 17:09 ` Paul Smith
2022-06-10 17:15 ` Segher Boessenkool [this message]
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=20220610171540.GT25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=fedor_qd@mail.ru \
--cc=gcc-help@gcc.gnu.org \
--cc=paul@mad-scientist.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).