Brendan (btrotter.delete@this.gmail.com) on September 14, 2021 4:30 am wrote:
> Hi,
>
> David Hess (davidwhess.delete@this.gmail.com) on September 13, 2021 1:00 pm wrote:
> > Daniel B (fejenagy.delete@this.gmail.com) on September 13, 2021 5:20 am wrote:
> > >
> > > Either the scheduler needs to learn the application behaviour
> > > or the application should come tagged, but then the ISV
> > > is expected to understand hardware and system energy
> > > efficiency, which they don't.
> >
> > Is there any reason not to expect applications to lie? Of course every
> > thread needs to operate on the fastest available core. Ask them.
> >
> > Alternatively why would developers spend time to distinguish which threads should operate on which cores
> > when the result can only make the perceived performance worse? And why risk getting it wrong?
>
> For desktop apps (and games, etc), it's not "my app vs. other processes", it's "my app's
> GUI thread vs. my app's background/worker threads". If you lie, you screw your own app.

Yes, we have a very simple solution for this problem: only spawn one thread per core, not one per logical processor.

-JLarja