Installera Steam
logga in
|
språk
简体中文 (förenklad kinesiska)
繁體中文 (traditionell kinesiska)
日本語 (japanska)
한국어 (koreanska)
ไทย (thailändska)
Български (bulgariska)
Čeština (tjeckiska)
Dansk (danska)
Deutsch (tyska)
English (engelska)
Español - España (Spanska - Spanien)
Español - Latinoamérica (Spanska - Latinamerika)
Ελληνικά (grekiska)
Français (franska)
Italiano (italienska)
Bahasa Indonesia (indonesiska)
Magyar (ungerska)
Nederlands (nederländska)
Norsk (norska)
Polski (polska)
Português (Portugisiska – Portugal)
Português - Brasil (Portugisiska - Brasilien)
Română (rumänska)
Русский (ryska)
Suomi (finska)
Türkçe (turkiska)
Tiếng Việt (vietnamesiska)
Українська (Ukrainska)
Rapportera problem med översättningen
https://www.techadvisor.com/article/746304/windows-11-2023-23h2-update-everything-we-know-so-far.html
shows the story nicely. Didsble all the e cores and avg fps stays same while the 1% low gets bump and 0.1% doubled.
Call me mr confirmation bias, but that was my predistion of the outcome years ago when the idea was introduced. For a nice palette of workloads. Sure, the e cores shine in bumping multicore benchmark values and if all you do is 7zip.
While the OS supposedly reads that info channel and try to do its best to juggle in the scheduler, the software we write very likely partition work to similar size and has only access to a single number of the hardware parallelism. So is actively mislead.
So just running the very basics of the OS Core but with background apps and services sitting idle not doing anything and then you just running Steam + Game this is why they wouldn't see much if any difference with E Cores disabled. You're not having them really doing anything
In some games just turning off hyperthreading gives a legit boost.
No it's not just turn it off or pause it. It's up to YOU to configure it. If you are about to load up a game make sure WU is configured not to be able to auto restart. Also enabling Game Mode helps also as this is a Do-Not-Disturb the OS has to stop WU from running in the middle of full screen tasks.
The reason for this is performance. I will try to explain: Let's use the Intel 13900KS as an example. The maximum out-of-the-box clocks for all-core loads for the p-cores for the 13900KS is only 5.4 Ghz. If you ran an all-core clock on this processor's p-cores then you would be limiting all cores to only 5.4 Ghz. But if we let it run it's boost and operate normally then up to 2 cores could run at 6.0 Ghz when playing games. Running a fixed all-core clock on that processor would mean that we would have to sacrifice -600 Mhz for gaming and that's just awful.
Running a manual all-core clock is actually slower and will reduce performance overall for all processes due to the reduced clock speeds vs letting the chips boost normally.
That's why I said "Usually but not always" in my comment above: not everyone knows how to do this or even will spend the time to do this. I would say that the majority of windows users do not ever touch or configure windows updates or even know that they can. I think that most people using Windows just run the game and leave everything in the system running as it normally would and they wouldn't know any different. In that scenario Windows update may run at random at any time.
Well if you not to spend the time to configure WinOS for Gaming then that's on you.
After the OS loads up you can go and Stop the Windows Update service and it should remained stopped for the remainder of that session. If you log off/on again or reboot it will come back on its own just as Defender will.
Exactly which processor do you have?
Yea I mean it's not something everyone can do especially with 13th Gen i7 or i9.
https://skatterbencher.com/2023/01/22/skatterbencher-53-intel-core-i9-13900ks-overclocked-to-6300mhz
Was definitely much easier to do on 9th and 10th gen but then again those also won't run as fast in the end.