From: "ross at burtonini dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29975] New: Search concurrency doesn't respect CPU affinity
Date: Mon, 09 Jan 2023 17:38:22 +0000 [thread overview]
Message-ID: <bug-29975-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29975
Bug ID: 29975
Summary: Search concurrency doesn't respect CPU affinity
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: ross at burtonini dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
I've a machine with lots of cores (256) but debuginfod doesn't respect CPU
affinity:
$ taskset -c 2 debuginfod -v
...
[Mon Jan 9 17:33:20 2023] (2351762/2351762): search concurrency 256
Instead of looking at the number of cores present, it should look at the number
of cores available to it (sched_getaffinity()).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-01-09 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 17:38 ross at burtonini dot com [this message]
2023-01-09 17:42 ` [Bug debuginfod/29975] " fche at redhat dot com
2023-01-09 18:24 ` ross at burtonini dot com
2023-01-10 23:04 ` fche at redhat dot com
2023-01-11 15:34 ` fche at redhat dot com
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=bug-29975-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).