This sounds like a simpler version of process lasso, definitely going to check this out.
this post was submitted on 18 Nov 2023
1 points (100.0% liked)
Intel
24 readers
1 users here now
Rules
-
Be civil. Uncivil language, slurs, and insults will result in a ban. If you can't say something respectfully, don't say it at all.
-
No Unoriginal Sources, Referral links or Paywalled Articles.
-
All posts must be related to Intel or Intel products.
-
Give competitors' recommendations only where appropriate. If a user asks for Intel only (i.e. i5-12600k vs i5-13400?) recommendations, do not reply with non-Intel recommendations. Commenting on a build pic saying they should have gone AMD/Nvidia is also inappropriate, don't be rude. Let people enjoy things.
-
CPU Cooling problems: Just like 95C is normal for Ryzen, 100C is normal for Intel CPUs in many workloads. If you're worried about CPU temperatures, please look at reviews for the laptop or CPU cooler you're using.
founded 11 months ago
MODERATORS
I recommend using Process Lasso proper. It's not hard to learn and much more powerful. CoreDirector looks like Process Lasso's Efficiency mode/CPU set/CPU affinity rules repackaged into one on/off toggle for every listed app.
You can do more interesting rules with Process Lasso like keeping non-interactive applications off of the highest-turbo P-cores or restricted to E-cores to improve idle power. My 60/60/60/60/57/57/57/57 13900K idles at 8-9W with MSI AB, Discord*, Steam, and other apps banished to E-cores and never allowed to turbo the P-cores.
*Discord gets 57x P-cores 6 and 7 as a treat.
Are there any easy to follow tutorials to use Process Lasso? Last time I used it, there was so much to it it was overwhelming.
I am setting up Process Lasso now, would steam high speed downloads get nerfed being only on E cores?
"as a treat" lmao
mine gets 3-31.
(before you read further always start with a full backup or at least a system restore point) I disabled hyperthreading on core 0 and using Microsoft's Interrupt-Affinity Policy Tool I have set gpu and mouse usb port to Core 0 and 1.
I'm a massive gaming nerd and was trying to "min/max" dpc / input latency.
Do not use the Interrupt-Affinity Policy Tool to edit SSDs, it will break your os.
Interesting. Going to try it out.
This is a part of ProcessLasso, also made by Bitsum. It works great, even ProcessLasso free version, which allows setting process afinity AND priority. CorePark also kicks butt, is free, and also by Bitsum.
There are paid versions of ProcessLasso and CPUPark which i use.
There’s already Process Governor. This is probably just bloatware.
Bitsum doesn't make bloat.
Let the OS and the hardware handle that. If there is an issue with the scheduling, report it.
The best solution is just to turn on the high performance mode in windows 11. Everything hits the P cores first and if the first thread is exhausted it uses an E core.
How does that go for background apps in performance mode. Do they go to the P cores first then to the E cores in performance mode?
The best solution is just to turn on the high performance mode in windows 11. Everything hits the P cores first and if the first thread is exhausted it uses an E core.
Enabling High Performance mode does not change the scheduling of processes...
So if this is possible, couldn’t it mean that we could start putting more background tasks on the E cores?
Yes that's what their already released process lasso software is for. This is just a simplified version of process lasso with less features.
Is process lasso worth using on Win11. Ive heard win 11 handles processes better then win10? PS 13700K z790.. Thanks.
Win11 does utilize cores better than win10, but specific programs like games or editing stuff does not discriminate, and Win11 thread scheduler is not advanced enough to dictate properly.
This way you have total control over your cores' affinities. ProcessLasso you also have control over process priority AND affinity.
I use ProcessLasso, takes a bit to set up, but 100% worth the results.
I doubt it achieves the same results as APO since APO works at a lower level
They do different things tho?
Edit: isn't APO about making the E cores work better and this just disabling them?
This can disable them yes but the main goal is to set apps running exclusively on P cores.
APO is just process lasso with tuned rulesets.
You can achieve similar boosts by setting R6 siege and metro exodus to have exclusive access to the P cores while relagating background tasks to the e cores.
Thats why only two games are supported right now, because it takes a lot of testing to make sure the game actually benefits from this kind of optimisation, cyberpunk 2077 for example will run worse if prioritised the same way due to it being optimised well to utilise the e cores for better fps.
We haven't yet seen benchmarks comparing APO with process lasso (at least I didn't see any so far) but no they're not the same, in theory APO should be more efficient given it has a specific driver and BIOS setting to do what it does.
That's what I meant by lower level. And I assume APO is doing something more than just splitting cores, hardware unboxed mentioned using only one e core from each section or something like that for better cache usage.
As far as I can tell, It might be working but I don't think it's working fully or as intended.
Here is testing I just did on a 13900k;
- Ran CoreDirector
- Added cs2.exe (Counter Strike 2)
- Confirmed process detection
When I run CS2, the process is detected and there is a nice graphic in Core Director that shows core utilization, and it has cores marked which are e-cores.
I just did a test with CS2 launch commands "-threads #' where # is the number of threads you want to cap CS2 at.
When I use '-threads 8' I can see that CS2 utilizes 8 p-cores with a p-core usage at 50% and e-core usage 0 or negligible. Seems to be working great - but I'm not sure that CoreDirector is doing this scheduling.
When I use '-threads 16' I can see that CS2 utilizes many e-cores and p-core utilization drops to 40-45%
When I remove the command entirely, I can see that CS2 activates all of the e-cores.
tl;dr - As I increase CS2 thread count, the process clearly increases e-core usage. It seems CoreDirector is failing to keep something in the process off of the e-cores.
I hate those stupid eco cores, I really, really do. You lost me as a customer when you introduced them Intel, which is not great for me because I'm not happy with AMD either. What a mess.
The problem is on the software side. Ecores architecture hybiridization is strictlly better that standard config.
I need to look into this thread later on in my downtime.
I know for a fact that games can still use E cores if you force efficiency mode off with Process Lasso. If you want to be absolutely sure that a game does not use E cores, you must use CPU sets or affinity.
A solution to a problem that doesnt exist
That must read pretty weird for someone who doesn't know what all this is about.
"We created a tool that prevents applications from using our CPU, you bought from us!"
So it's a slimmed down free version of Process Lasso then.
i tried,. and its bad,.
if you want to switch off E-cores > use only BIOS (not process lasso or coredirector or taskmanager)
if you dont like to disable e-cores > use heterogeneous policy 0 in powerplan,.
On i9-13900HX, it does not consider cores 14 and 15 as P for exes you set in the list.