Recent Posts

Pages: [1] 2 3 ... 10
1
Great!

BTW, Process Lasso has a tool to allow you to adjust these same settings. It is called the Tweak Scheduler. You can get to it via 'Tools / Tweak Windows NT scheduler parameters'. There is no particular advantage to using it over the Windows control panel settings, but it is a little more detailed (or confusing).

2
Hi,

the two links were awesome ;) Found some time and wrote a blog article and gave Bitsum / you credits for giving me the missing information.

Many thanks for the information !! ;)

https://www.tonstudio-forum.de/blog/index.php/Entry/92-Windows-Optimale-Leistung-anpassen-f%C3%BCr-Hintergrunddienste-weiterhin-erforderlich/
3
Hi,

I am talking about Windows 7 / 10 Professional, this setting here (sorry only German version here, but I think you know what I mean when you see it).

I need to look at the links at another day, already got late ... many thanks for your time and providing the links.

 
When you have time to read the first two links I posted above, it pertains to those windows settings.
4
Yes, that is what we are also talking about.

There is no general guidance as to which setting is better for audio tasks. I would leave it alone.

Background programs are simply those that don't have the keyboard and mouse focus. When 'programs' is prioritized, the application that has the keyboard and mouse focus gets more CPU time slices.

Process Lasso does not change this setting.

5
Hi,

I am talking about Windows 7 / 10 Professional, this setting here (sorry only German version here, but I think you know what I mean when you see it).

I need to look at the links at another day, already got late ... many thanks for your time and providing the links.

6
Process Lasso / Re: Cpu rule, problems & some ideas
« Last post by Jeremy Collake on Today at 12:56:18 PM »
Unfortunately, it is not trivial to identify the cause of such responsiveness dips.

These can occur intermittently, and are sometimes caused by power state transitions. Other times, one or more Windows subsystems experience a delay for any number of reasons.

Process Lasso's system responsiveness metric doesn't have any knowledge of why the dip occurred, and there is no reliable way to generically determine the culprit.
7
Process Lasso / Re: Cpu rule, problems & some ideas
« Last post by Unico on Today at 09:36:39 AM »
Thank you for appreciation :)

A question:
Is there the possibility of understanding what could cause a sudden lowering of responsiveness (not even the complete actions log, reports anything about it), which "casually" (but I don't think it's casually) appears even if the PC has no active application or under stress? it would not be bad, if possible, to have given a statement of the cause of this lowering.

Thank you again.
8
Here is my 2 cents:

#1 - See Ed's links.

#2 - It probably doesn't matter for most people, but it's hard to say with certainty (as Ed said). Contention for the CPU can occur easily and interrupt real-time tasks like audio processing and playback. That said, it's then hard to say which setting is most often effective at limiting the effects of contention. There are a lot of user, device and application factors. If it were me, I'd just leave it alone, defaulting to foreground for Workstations and background for Servers.

#3 - These CPU scheduler settings aren't being changed by Process Lasso.

Lastly, you asked what makes for a 'background' process. It is everything BUT the window of the application you are actively using (has keyboard/mouse focus). That is called the foreground process.

Ed gave good general guidance.
9
Thanks, I read it, up to that level I am familiar with your product.

I try to rephrase to bring my question more to the point:

1. what happens inside of Windows when I choose the setting to optimize Windows for background tasks
    its not documented, I hope that you have that much insight, when programming such a tool as Process Lasso

2. whether its still applicable to to priotize background services, when working in the area of Music Production (Mixing, Mastering) and why.
    Some people think/argue that modern CPUs, SSDs are so powerful, that the root cause for this setting potentially does not exist anymore.

3. whether the windows settings, to optimize windows for background tasks, are being changed further by Process Lasso.

Many thanks
Ok, Are you running Windows server editions or work-station ones?
The server version are prioritized for background processes and the standard workstation is for foreground processes. The Windows scheduler does these adjustments.
I don't have personal experience with high-end audio stuff but my understanding is to use server versions or set to background processes in windows settings.

Here link about this part of OS.
https://www.thewindowsclub.com/processor-scheduling-in-windows-7-8

More in-depth
http://recoverymonkey.org/2007/08/17/processor-scheduling-and-quanta-in-windows-and-a-bit-about-unixlinux/


What I would try is setting windows to prioritize background and running PL with default values and then exclude the audio processes that you work with from Probalance.
That is under advance settings in PL options.
See how that works and if needed you could also raise one or two of the audio workload processes CPU priority but I would go slow and even see if it is needed.

As for windows background services, if you mean the setting in Probalance advanced options ("exclude system services from restraint"), I would leave it checked but again you could experiment with this too. It shouldn't affect, windows processes like indexing and other maintenance processes "should" only kick in when the system is idling.
This doesn't always happen so need testing.

Overall I can't give exact settings cause there are too many factors and variables, I can only give a general guideline.
On
 "3. whether the windows settings, to optimize windows for background tasks, are being changed further by Process Lasso."
Probalance alters the CPU priority when the CPU% load of a process goes above the specific values set in settings.

https://bitsum.com/how-probalance-works/

By default, this is done to background processes, so a normal process ould be lowered to below normal until the load lowers. This is why in this particular case you want to exclude your audio workload processes.
This way any other background will be restraint so your workload processes are less affected by the load.

Also think of the CPU priority settings (idle, below normal, normal, above normal, etc) as a pie chart so the higher priority values will give the processes more, a larger slice of the CPU pie. That is a crude way to visualize it.

Hope that helps
Ed
10
Thanks, I read it, up to that level I am familiar with your product.

I try to rephrase to bring my question more to the point:

1. what happens inside of Windows when I choose the setting to optimize Windows for background tasks
    its not documented, I hope that you have that much insight, when programming such a tool as Process Lasso

2. whether its still applicable to to priotize background services, when working in the area of Music Production (Mixing, Mastering) and why.
    Some people think/argue that modern CPUs, SSDs are so powerful, that the root cause for this setting potentially does not exist anymore.

3. whether the windows settings, to optimize windows for background tasks, are being changed further by Process Lasso.

Many thanks
Pages: [1] 2 3 ... 10