Hello all

I've been investigating ways of reducing the CPU 0 usage on my o/c i7 6770K as it was almost always sitting at around 98-100% (P4.5 HF2).

During the process, I've just noticed that, whilst P3D is still running (full screen), if I switch to Task Manager, select P3D, untick <all Processors> and just tick CPU 0, then immediately swap back to ticking <all Processors>, when I return to P3D, my CPU 0 usage has dropped way down to between 40 and 50%, and there it stays, give or take a few percentages. I've tried the 'placebo' effect of this by just opening and closing Task Manager, but it's definitely the toggling of the AF that makes it occur.

I'm just wondering is anyone could explain what might be going on here and if there's a way of 'automating' the above without diving into Task Manager ? 

Regards

I read much about this here and in the LM forum and have come to the following conclusions:  First, it is wrong to think that core0 fully loaded is a bottleneck.  LM has explained that they design the work flow such that this is intentional and they take advantage of multicore environment. 

Second, I've played with the exact thing you observed that by toggling core0 off and on it seems to redistribute the loading.  However, I've never found that doing this has any impact on performance, frame rate, stuttering, long frames or anything that could be either quantified or qualified.  It's a big no deal.

On 11/10/2019 at 7:05 PM, downscc said:

It's a big no deal.

Agreed.

I don't think Task Manager measures core usage reliably. I've been advised to try HWINFO or RTSS for this, which I will be doing starting today!

Pete

 

10 minutes ago, Pete Dowson said:

Agreed.

I don't think Task Manager measures core usage reliably. I've been advised to try HWINFO or RTSS for this, which I will be doing starting today!

Pete

 

I probably should have mentioned that all core usages were being monitored live in P3D using RTSS. 

On 11/12/2019 at 2:47 AM, Pete Dowson said:

Agreed.

I don't think Task Manager measures core usage reliably. I've been advised to try HWINFO or RTSS for this, which I will be doing starting today!

Pete

 

My HWINFO application launches on startup of Windows.  It's great.

The only reason I do the task manager affinity thing is that I have P3D config set to use a specific set of cores. I also use Process Lasso to move ancillary programs I use with P3D to cores not used by P3D. If I don't do the affinity thing, TrackIR movement is somethimes slow and stuttery, but after the affinity trick it's smooth as silk. With that said, I notice NO improvement to P3D fps or P3D stutter issues. I only ever experience stutters when my GPU can't keep up (DL and SSAA) or CPU bottlenecks (too high scenery settings with complex aircraft). Normally I get solid 30 fps (fixed in P3D) that doesn't stutter, except for the scenarios previously mentioned.

Kind Regards,

For what it's worth, my usage of Process Lasso (not just the AM function) has increased the stability of P3D. I used to get random crashes quite often (Kernalbase, etc.) Now if I get one crash in 3 months, it is a lot.

 

You guys that lose Process Lasso, do you run a script to start apps on different cores or just have Process Lasso switch after they start? I'm thinking of trying it out again since I've been getting more stutters lately.

On 11/4/2019 at 5:51 PM, Chapstick said:

I

 

4 hours ago, bbain1187 said:

You guys that lose Process Lasso, do you run a script to start apps on different cores or just have Process Lasso switch after they start? I'm thinking of trying it out again since I've been getting more stutters lately.

I bought the full version. With that, you just do the settings you want and you have the option to keep those permanently. So no scripts, zilch, nada. Easy ka-peasy.

4 hours ago, IanHarrison said:

 

I bought the full version. With that, you just do the settings you want and you have the option to keep those permanently. So no scripts, zilch, nada. Easy ka-peasy.

Agreed. I have Process Lasso explicitly assign P3D to all 8 cores, and restrict AS, ATM, et al to Core 1. When everything works it is nice and smooth and my overall system busy is around 70-80 percent.