Recent Posts

Pages: 1 ... 7 8 [9] 10
81
So this logging issue happens only with linked processes of FL Studio and itself?

No other windows or other programs show this issue?
82
I'm not sure if FL Studio by itself is necessarily the issue but I believe that after adding mutiple VST plugins to the software, I started noticing the issue. Unfortunately, I'm not sure what plugin started causing the issue as I had added quite a few new VSTs in a short timespan. Hopefully that will give you something to go on. I do notice that after I close out FL Studio, the ILBridge.exe process and FL64.exe will stay in Task Manager and I will have to forcefully end the tasks. This is when Process Lasso begins to continually show that the task has been started and stopped continually in the log section of the software.
83
Can you, by chance, advise any usage scenario of FL Studio where we are likely to see this effect? We are trying to reproduce it.

Thank you
84
General / Re: Cpu affinity doesn't change by the rules
« Last post by Jeremy Collake on October 16, 2020, 09:10:56 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.
85
Quote
How come Windows doesn't do this itself, a basic garbage-collection of standby memory routine? Are there any costs to doing it, like will other apps that have stuff in standby memory see performance hits as they each have to use resources to reload things into memory?

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 ;).
86
General / Cpu affinity doesn't change by the rules
« Last post by empleat on October 16, 2020, 08:41:48 AM »
Well this is strange. In process lasso, under rules affinity is set to 0-5, but cpu affinity is 1. Even if i change it again, it keeps reverting to 1. Even if i select always. Process is steam and steamwebhelper. Than my game has also 1 core and i can't change it, unless i change it for steam. But it keeps reverting to 1. I didn't change any pro balance setting. And tried different profile, didn't help. No idea why it does that...

Thanks for help.

EDIT: restarted steam and process lasso, now it is fine, never mind.
87
Process Lasso / Re: Does clearing/trimming/purging standby memory/RAM actually help?
« Last post by edkiefer on October 14, 2020, 07:30:56 AM »
Interesting, thanks for the info. Now that you mention, there is a game I play that after time it starts to get stuttery. I just assumed it was poor programming on the game's part (not to say that isn't the case) and the game or system needed to be restarted. I'll try this next time it happens to see if it clears it up.

How come Windows doesn't do this itself, a basic garbage-collection of standby memory routine? Are there any costs to doing it, like will other apps that have stuff in standby memory see performance hits as they each have to use resources to reload things into memory?

Do you still use this function (despite not seeing it since 1909)? Would there by any downside or cost to having this set to run automatically/routinely? TIA
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.
88
Hi, The main user base for that function is gamers and yes it basically does the same as what ISLC does.
As far as what it does is to clear standby list memory but the reason can vary but the short of it is around Win10 1809 some games would start to stutter after a while and clearing the standby list would help fix this.
Now for me It only happened after a long time of gaming in a single game map and around Win10 1909 I don't really see the issue but you will get different answers there it seems to depend on the game and system.
If you don't suffer from stuttering after a while then no need to enable it, due note stuttering can be happening because of low free memory too.
Interesting, thanks for the info. Now that you mention, there is a game I play that after time it starts to get stuttery. I just assumed it was poor programming on the game's part (not to say that isn't the case) and the game or system needed to be restarted. I'll try this next time it happens to see if it clears it up.

How come Windows doesn't do this itself, a basic garbage-collection of standby memory routine? Are there any costs to doing it, like will other apps that have stuff in standby memory see performance hits as they each have to use resources to reload things into memory?

Do you still use this function (despite not seeing it since 1909)? Would there by any downside or cost to having this set to run automatically/routinely? TIA
89
Process Lasso / Re: Bitsum Highest Performance Mode vs Ultimate Performance mode
« Last post by Coldblackice on October 13, 2020, 11:45:12 PM »
BHP starts from a clone of 'Ultimate Performance', if it exists (it may be hidden). If it doesn't exist, then 'High Performance' is cloned. From there the *only* modifications are to disable below base CPU frequency scaling and CPU core parking. The USB selected suspend setting is not altered by Process Lasso.

I don't have any additional guidance on whether you should enable or disable USB selective suspend.
The main reason you see this option mentioned or used is for a workaround of a USB2 device that loses connection from the system (goes to sleep and never wakes up). Disabling this option through power plan or Device manager stops the idle condition, but at a cost of more power usage.

Probably not an issue on desktops but may matter on laptops.

Here one example link.
https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

Thanks. I don't have issues with any of this myself, was just trying to make some sense of the two guys above perceived differences between plans, if there legitimately are any differences and if so what those could be. Seems that the most likely scenario is that this is a placebo.
90
I did try disabling problematic processes but it looks like it's still showing those programs. I'll just have to set the program not to log starting processes as well for now.

Thanks!
Pages: 1 ... 7 8 [9] 10