High perf vs balanced mode for power settings won't change a thing for XI (at least on win10) since it's really not about core parking. It's about the fact FFXI doesn't tell the CPU it needs ressources. Since the cpu, parked or not, sits almost at idle to save energy. And even on high performance, the default settings on win10 for minimum processor state is 0% (at least on laptops, even while plugged)
This does not logically make sense to me.
IF what you says its correct then balanced vs high performance mode would make a difference
That has nothing to do with core parking that has to do with P states switching
Coreparking was just mentieodn because its the only feature of power savign settigns thta has shown an objectively meauserd differente
Balanced VS high performance is a lot more than just core parking. it seems like your statements is saying that is the only difference...
to put id idffent
if this is the issue
<i>It's about the fact FFXI doesn't tell the CPU it needs ressources<i>
The chaning poer setting would make a difference sicne epthe power stign changes P states. and what you are talking about is p state.
even though Software dont TELL if they need cpu ressources.
the cpu scheduler handles out cpu time for threads that are ready to run on the core.
But i am assuming you are just trying to do a high level not tech explenation of the process
But bottom line is software does not have to do anything to get CPU ressource sbesides exist/ the CPU schelduer will handle out cpu accordingly
Which is why the entire premies of you stamens evne correct for what high perofmrance and balacned modes accutally does. seems inccorect.
This above has nothing to do with core parking
Dealing with Coreparking
Coreparjing puts the cores in a Very Low C states ( not p state) which has a very slow time to get back to C0 states where the Core can actually execute code.
Windows 7 uses this on evey other logical cores. which can be benefician on system with SMT ( not going into that now)
Windows 10 does it by slowing down pairs of logical cores. which can be severely hardmful for perfrmacne as lgocial cores to a SMT system is in pairs connected to the physsical core.
aka windows 7 leave all physsical cores availbe windows 10 does not.
Correct that Coraprking is not enabled in windows 10 balanced
However it is still a features that is avaible
sideinfo: the AMD ryzne pwoer palns changes coreparking in windows 10 to work like it does in windows 7 aka evry other logical core locked down
Beside the slow time from goign from C6 to C0 for the core to be ready to execute time when a threa is scheuled for it
Coreparking has another fundemental flaw
Windows does not take affinty into consideration for releasing cores from locked status.
so if you sotware is set with affinity to run on logical core 0 and 2 on a system with 4 logical cores.
and there is no load on logical core 1 and 3
logical core 0 and 2 will enver be unlocked as there is plente of ressoruces free according to windows. however those rssoruces are never abaield to the process thas is affinity controlles to core 0 and 2 and your software never gets any cpu time.
TLDF:
What you are syaign does not make tecnhical esence on how high vs balced works
Even if we correct it . that is now how it works ( or should work)
Me mentioning of core parkinh was simply to states that that is the ONLY performance improvent i have seen coming from messing around with balanced vs high performance. and the rest of the difference is close to none existing.
as always if you have objective metrics on this i would be happy to see them