Recent Posts

Pages: 1 ... 6 7 [8] 9 10
It would be awesome if there was an ability to select/click/highlight points or areas on the graph and then have a floating popup reveal information about what was occurring at that point in time.

For example, if I look at the graph and see a "V" shape cut into the Responsiveness plot line, it would be highly useful if I could mouse over to that "V" on the graph, click, and then a floating popup appears showing what the top-5 CPU-using processes were at that time (or RAM/commit, I/O, Network usage, etc).

Also useful might be graphing timestamps on the X-axis to help correlate what was occurring at those moments. This usefulness would be compounded if there was an ability to choose the time-increments, like 30-sec intervals, 5-min, 15-min, 30/60/etc. Obviously the graphing would change along with these changed intervals.
Windows has a very good memory management system, the idea behind the Standby list is to use it by windows (let if fill) so that if you run something again it is in the cache. As soon as you run a new application if standby is full it should free from the standby list whatever is needed and it seems when it's right on this edge that some games and apps get the stutter.
So you can try it, also know you can enable just standby clearing w/o SmartTrim too.

PS: For me it went away in Win10 1909+ versions.
Windows does try to manage this cache (standby list) already, removing less frequently referenced data. There is a penalty to flushing the cache, but it is usually short-lived.

I don't recommend casual use of this function, and most people should not use it.

Is it beneficial? Well, maybe there is sometimes a performance problem with this cache that is resolved when it is purged.

In any event, gamers wanted it, so I added it ;).
Gotcha, thanks guys. Makes sense about it being a gamer's request, lots of snake oil tweaks spread around the gaming community alright :)
General / Re: If we want BSM price up, what we need to do ?
« Last post by Coldblackice on October 23, 2020, 09:40:25 PM »
 ;D ;D ;D
Hi there! I guess I will just have to restart the computer every now and then when I see those items pop up in the logs (right now I have those messages suppressed). Unfortunately, the zombie processes never show in Process Lasso after they have been terminated so there is no thread count to see. They will only show up in the logs. Hope that helps!
General / Re: Cpu affinity doesn't change by the rules
« Last post by Jeremy Collake on October 20, 2020, 12:16:21 PM »
Well, *something* was putting them to 1 ;).

Let us know if it reoccurs!
You could maybe sign the user out, but that's not much better than a reboot. There might be something else that could be done to terminate them, but it would require researching the underlying cause of the 'hung' instances.

Can you tell me the thread count for those zombie processes? This is shown in Process Lasso, or the Task Manager Details pane if the 'Threads' column is enabled. If it happens to be 0, I may use that as a work-around.

General / Re: Cpu affinity doesn't change by the rules
« Last post by empleat on October 16, 2020, 11:08:45 AM »
My first guess might be you are seeing a CPU affinity inheritance from steam to its child process(es). If you've set rules for Steam, be aware you'll need to set other rules for your game processes to prevent Steam rules from propagating to the children. Let us know if it happens again and post your INI file contents here.
I didn't set rules. It was putting it to 1 for some reason. Doesn't matter anymore.
If this is the case, it would sound like Windows isn't completely shutting down the processes either. Short of rebooting the PC, would there be a way to have the OS completely terminate the processes?

It sounds like FL64.exe and ILBridge.exe are stuck in some type of exception state that isn't being properly handled.

This unusual process state is confusing Process Lasso, though it doesn't have any real consequence apart from the logging.

Resolution may require some re-architecting, so the problem may continue in the next final version. However, we are tracking it, and it will get resolved in time.

Thank you for the additional information!
That's correct. I've only seen this happen so far with FL Studio and its associated processes.
Pages: 1 ... 6 7 [8] 9 10