From: Joel Brobecker <brobecker@adacore.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10.1 release: branching early July?
Date: Tue, 16 Jun 2020 11:13:13 -0700 [thread overview]
Message-ID: <20200616181313.GO7711@adacore.com> (raw)
In-Reply-To: <ydd7dw7ce88.fsf@CeBiTec.Uni-Bielefeld.DE>
> I've now found where those are coming from: the thread name "gdb worker"
> visible in ps -L provided the necessary clue. They are due to worker
> threads now being enabled by default. On my desktop with 4 cores and
> hyperthreading, that's relatively harmless. However, when I run gdb on
> an 8-socket server with 160 cores total, the messages about thread
> creation when debugging gdb are killing you ;-) I traced this to
> maint.c (update_thread_pool_size) where the count defaults to
> std::thread::hardware_concurrency (). Maybe a bit over-eager...
Oh my....
I remember that this version of GDB makes parallel minimal reading
the default. I think you can throttle down the number of threads
using:
maint set worker-threads N
--
Joel
next prev parent reply other threads:[~2020-06-16 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 1:56 Joel Brobecker
2020-06-14 2:04 ` Simon Marchi
2020-06-15 22:53 ` Joel Brobecker
2020-06-18 19:57 ` Pedro Alves
2020-06-14 15:14 ` Rainer Orth
2020-06-15 23:09 ` Joel Brobecker
2020-06-16 13:49 ` Rainer Orth
2020-06-16 18:13 ` Joel Brobecker [this message]
2020-06-14 15:32 ` Hannes Domani
2020-06-15 23:17 ` Joel Brobecker
2020-06-16 20:28 ` Tom Tromey
2020-06-14 16:53 ` Philippe Waroquiers
2020-06-14 16:57 ` Philippe Waroquiers
2020-06-16 0:13 ` Joel Brobecker
2020-06-26 11:36 ` Luis Machado
2020-06-26 16:26 ` Joel Brobecker
2020-06-26 19:27 ` Luis Machado
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=20200616181313.GO7711@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).