public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: posix thread scaling issue
Date: Sun, 03 Sep 2023 08:13:08 +0200	[thread overview]
Message-ID: <87h6obss23.fsf@Rainer.invalid> (raw)
In-Reply-To: <076456ca-2c5d-4bb3-a64b-97ed4bdd26ce@jeffunit.com> (jeff via Cygwin's message of "Sat, 2 Sep 2023 13:04:10 -0700")

jeff via Cygwin writes:
> According to the task manager, it says 'Sockets: 1'.

That number doesn't matter at all.  When you have more than 64 logical
processors, you will have processor groups regardless of topology.
Below that threshold processor group configuration can be influenced
both by BIOS settings and Windows boot parameters.  The TL;DR; is that
you should configure your box to have a single processor group whenever
possible unless your applications either never use enough threads to
need more threads than there are in any single group or they are
processor group aware.  The latter thing means you need to assign each
thread that should run on a different processor group than the main
program manually to its respective group unless you run on Windows 11 /
Windows Server 2022 or later.  There is a set of new functions to
control that behaviour whose interaction with the old affinity interface
and defaults is not very clearly documented.

So it seems your best bet would be to either modify your application or
upgrade to Win11.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2023-09-03  6:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-02 14:57 jeff
2023-09-02 17:56 ` Brian Inglis
2023-09-02 18:27   ` jeff
2023-09-02 19:59     ` Brian Inglis
2023-09-02 20:04       ` jeff
2023-09-03  6:13         ` ASSI [this message]
2023-09-03  3:50       ` Mark Geisert
2023-09-03  4:13         ` Mark Geisert
2023-09-02 19:30 André Bleau
     [not found] ` <e36d50d5-75d0-40d5-92e2-02d04092fd77@jeffunit.com>
2023-09-02 21:23   ` André Bleau

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=87h6obss23.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /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).