Severe lag spikes, using Process Lasso

[Thomasso 224]

Hello,

I've run into a strange issue. I did some changes in CPU core assignment. I'm using Process Lasso. 

This is what I have set up:

• Process Lasso mode: High performance
• P3D cores: 2-7, high priority
• All add-ons: 0-1, normal priority

I usually get very good fps on my system (see signature). But after I started using Process Lasso, I get severe lag spikes sometimes. It's mostly random. And by lag spike, I mean the whole computer, meaning that I can't even move the mouse cursor (I can but it's really slow and unresponsive). It goes on for perhaps 30 seconds and then back to normal. 

In Process Lasso, it's represented by the red graph drops, if you are familiar with the SW. The problem is visualised here: https://ibb.co/hHpHu7 There were 2 lag spikes. 

I have no idea where to even begin debugging this, so I'd be grateful for any advice... Thanks very much :)

[vgbaron 3,590]

start turning off your addons to see if you can determine which might be affecting your performance.

 

Vic

[Thomasso 224]

2 minutes ago, vgbaron said:

start turning off your addons to see if you can determine which might be affecting your performance.

 

Vic

Are you sure it's caused by an add-on?

[patrice_bambou 85]

Don't use high priority, it will stuck your system (all system services behavior will be problematic) .

Let P3D at normal priority and even low priority, and things will go better, far better.

Patrice.

[Thomasso 224]

6 minutes ago, patrice_bambou said:

Don't use high priority, it will stuck your system (all system services behavior will be problematic) .

Let P3D at normal priority and even low priority, and things will go better, far better.

Patrice.

Huh, interesting. Who would have thought? I set it to "Below normal" and it's smooth as silk. Thanks! :) I will test and report if the issue goes on.

[jcorstjens 63]

Hi Thomasso, this is what I call true coincidence!

Tonight I was making a flight with the F1 B200 (GTN750&650) from KBLI to KHQM. I had seen those arrests frequently in the past months, but never so long lasting, similar as you also describe it. I also use Process Lasso for  a long time now and tonight I also observed thast the arrests were simultaneous with the red line coming down in the graph. As the arrests were so pronounced I decided to switch Lasso off and continue flying. To my observations the arrests were much less frequently and also were much shorter in duration (more like stutters). I don't claim yet that the arrests are caused by Lasso, but I will certainly be more critical in using Process Lasso. I am using the freeware version of process Lasso. I am unfortunately not sufficiently skilled into microprecessors and processes to be able to trouble shoot this phenomenon.   

[Thomasso 224]

2 minutes ago, jcorstjens said:

Hi Thomasso, this is what I call true coincidence!

Tonight I was making a flight with the F1 B200 (GTN750&650) from KBLI to KHQM. I had seen those arrests frequently in the past months, but never so long lasting, similar as you also describe it. I also use Process Lasso for  a long time now and tonight I also observed thast the arrests were simultaneous with the red line coming down in the graph. As the arrests were so pronounced I decided to switch Lasso off and continue flying. To my observations the arrests were much less frequently and also were much shorter in duration (more like stutters). I don't claim yet that the arrests are caused by Lasso, but I will certainly be more critical in using Process Lasso. I am using the freeware version of process Lasso. I am unfortunately not sufficiently skilled into microprecessors and processes to be able to trouble shoot this phenomenon.   

Hi jcorstjens, check out the advice from Patrice above. It seems that the issue has been solved by that. I suppose you have P3D set to high priority in Process Lasso? It was recommended in some guide. I use the Pro version but essentialy it's the same I believe.

[jcorstjens 63]

Yes Thomasso, I followed the advice, now everything set at "below normal". At this moment almost finalising the return flight and indeed no arrests anymore!

Thank you for bringing this up and Patrice for bringing the solution!

[Thomasso 224]

1 minute ago, jcorstjens said:

Yes Thomasso, I followed the advice, now everything set at "below normal". At this moment almost finalising the return flight and indeed no arrests anymore!

Thank you for bringing this up and Patrice for bringing the solution!

Sure, no problem! :) However, I ended up on "Normal" priority. I don't see a reason why P3D should get lower priority than anything else. No spikes either!

Cheers!

[SKEWR 364]

I love using Process Lasso. What works for me is P3D at Normal and then limit CPU usage for addons.

 

For example (I do not turn off HT). P3D set up as a highest Bitsum Performance. Active sky can cause process restraints if I limit it's use to say say cores 4-7.Therefore AS16 is set to cores 2-7. TrackIR and LINDA I set to 4-7. Coatul (sp) is set to 6 & 7. The heavier the processor load of the addon, the more cores I give it. Doing this I usually have good results with no process restraints.

On a side note, the common consensus is to leave everything off of core 0 and 1. When I do this for P3D I get great frames, but I risk, occasionally, the scenery not loading and a ton of blurries. So even though having P3D on cores 2-7 or 1-7 yields great FPS results, I'd rather get good visuals as well.

[GSalden 4,656]

Use an AM for P3D , batchfiles for Fs addons ( = setting an affinity for an addon at startup ) and leave everything else to PL. That’s how I have it 

Use Search to find out why P3D should not be controlled by PL....

Edited April 16, 2018 by GSalden

[ideoplastic 86]

I have been using Process Lasso for a few years and when P3D v4 came out contacted the developer asking his advice on what settings in his opinion I should use for the sim. His reply was that to just use default settings. I have to admit I was surprised by his advice but to date all is running well and haven't had any issues issues. For what is worth.

[AnkH 2,261]

8 hours ago, GSalden said:

Use an AM for P3D , batchfiles for Fs addons ( = setting an affinity for an addon at startup ) and leave everything else to PL. That’s how I have it 

Use Search to find out why P3D should not be controlled by PL....

Dear Gerard, could you please elaborate a Little bit how you set an affinity via batchfile for an addon? I finally found a good AF for my P3D by keeping it off from cores 0 and 1 and it would be nice to have Active Sky limited to those two cores only. Thanks in advance...

[GSalden 4,656]

3 hours ago, AnkH said:

Dear Gerard, could you please elaborate a Little bit how you set an affinity via batchfile for an addon? I finally found a good AF for my P3D by keeping it off from cores 0 and 1 and it would be nice to have Active Sky limited to those two cores only. Thanks in advance...

Written by SteveW :

http://www.codelegend.com/forums/viewtopic.php?f=2&t=632

[cleonpack93 79]

I actually recommend removing the CPU affinity settings in Process Lasso. Process Lasso is built to balance everything across all cores, and I found when I removed all the affinity settings and just let PL do its thing it worked a lot better.