Fix game stutter on Win 10 1703-1809

I noticed that Metro Exodus is incompatible with these standby cleaning tools, the game stutters even more and becomes unplayable. Meanwhile some games I have to set ISLC to be very agressive (Battlefield 1, Quantum Break) to play smooth. I just wish microsoft or nvidia fix this mess.

 

I've noticed that after playing some Destiny 2 and then switching to Hunt Showdown standby list grows to a point there is 2-5MB free memory game is hitching mess after that. Clearing fixes all of the hitching for the rest of the game and standby list won't grow no more during Hunt Showdown and after closing the game. Would seem like some of the apps linger more and some don't. Good thing people have workarounds available. Thanks for you guys for helping.

 

That is not an incompatibility with ISLC, the game is actually using the newly released space and you're ending up with an OoM scenario either through the DX12 memory leak or actual lack of ram.

 

In my case, it seems this game actually uses the resources it puts on standby list (just guessing) because if ISLC clean the list the game just hangs and the textures reload and the game keeps stuttering until the standby list is the same size it was before. Also I have 16gb RAM which is more than recomended specs. Moral of story: this game runs better with ISLC off. Anyway this game is such a disappointment, I loved previous Metro games and couldn't bother finishing this one.

 

I was thinking on adding some sort of exclusion list or allowed program list in the future.
No promise tho. That will depend on my motivation / free time.

 

I can provide you with module which will either check for running apps or monitor for starting and finishing apps.
For example, class which accepts a list of apps to monitor and notifies to disable or enable the purging (or overall sampling of the memory).

 

My arms are wide open

 

OK, day or two... I have all pieces of code for that, just need to assemble them in one piece.

PS I just hope that C# will be OK for you. If not directly then as a .Net assembly.

 

It's perfect ISLC is in C#

 

Nice. My VisualBasic skills are rusty a bit...

 

@Wagnard

Here you go
http://www.mediafire.com/file/t7h2oueppfhku6v/AppsMonitor.zip/file

A class and a console app as an example.

PS Class code uses WMI and the app should be executed with enough level.

 

Thanks, will check and add it when I have a little free time. (weekend probably)

 

Some thoughts about WMI optimization came to me. Will test them tomorrow...

 

@Wagnard

Updated
http://www.mediafire.com/file/t7h2oueppfhku6v/AppsMonitor.zip/file

PS There is alternative to WMI events - processes can be polled. This will eliminate the need for elevation, but unavoidably will increase the CPU usage with every poll (even if instead of WMI the polling will be made with Win API - I have such code too).

 

Nice, seems to work quite well.
Except is I try to run "monitor.IsAppsExecuting" from another thread where it will return "false" when a "notepad or cmd" is open before ISLC launch. Currently investigating why.

 

I would think an exclusion list would have the most utility. I've been using this to keep Win 10 in good shape to support a variety of game and image processing applications that have demanding memory requirements. For me, it would be simpler to list the occasional something that can't deal with having the standby memory allocation reset than to enumerate everything else.

p.s. Process Lasso has recently (31 Jul 19) updated their Smart Trim functionality to address this issue as well. I've been a long time user of PL and respect their perspective on subjects like this, and their validation of the need is gratifying. In any event, I still prefer to use ISLC to optimize this aspect of Win10 on my system.

 

Yep I'm was going to go with the exclusion list.

 

Because there is no polling of running apps. We only used notifications about newly started processes to store the process IDs, so that when process launched before ISLC finishes its process ID is not in the list. To cover that we need to add polling on the start of ISLC. Or just ignore, because I doubt games are scheduled with the help of Task scheduler. Also you can simply state - if you want exclusion list, launch ISLC before your apps.

I have the code for polling, so if you decide to include that, I will update the sources.

 

It's weird because if I'm not checking from a new thread, it is working.
Anyway I'm testing something at the moment that seems to work. Just verifying if it doesn't eat too much CPU.