Process Lasso’s installer auto-corrects if you get the wrong edition or bit size (32 or 64), so have no worries about the right download link. Process Lasso Server Edition will always install on all Windows Server OSes. The normal workstation edition will otherwise install.
For Windows workstations such as Windows 10, please buy a Workstation license.
For Windows Servers, such as Windows 2016, please buy a Server license.
The correct edition of the product will install no matter which download you select. Windows Server OSes require the Server Edition, so it will install on them. You can check which edition was installed via the product About dialog, installer caption, and other areas.
Yes! We stand behind the quality of our products and will refund 100% of your money for any reason. You have 30 days from the date of purchase to request a refund.
Licensed users are entitled to product updates within their subscription period. The period can be annual or lifetime. In the case of lifetime license, the user is entitled to all updates, including new major product versions.
Workstation: Windows 7, 8, 10.
Server: Windows 2008, 2008R2, 2016, 2019.
Memory and disk requirements are negligible.
Open your Process Lasso GUI, navigate to the Help menu and select ‘Activate this software’. Paste your license activation key (see Order History to find yours) into the dialog. Then click ‘Activate now‘.
If you do not see options to Activate, then the product is already activated. You can confirm in the Help/About dialog.
No. Process Lasso does not system modifications that persist after it is uninstalled.
NO! The ProBalance feature doesn’t actually ‘restrain’ anything. We used that term only for lack of a better one. ProBalance’s default action is to simply temporarily lower the offending process’s priority class to Below Normal, a marginal change to the precedence during contention. In real-world and synthetic tests, as shown in the CPUEater demo, this is all it takes to restore responsiveness to the rest of the PC, and it certainly doesn’t impact the performance of targeted applications.
There is no perfect answer to your question. The defaults settings are the most tested and should work best for most people. In general, ProBalance has to be a little aggressive to hit processes *before* they cause a responsiveness problem. This aggressiveness is not an issue since the marginal adjustment it makes to priority classes doesn’t have any negative impact. It won’t slow a process down, for instance. The priority class only ever matters if there is a lot of contention for the CPU. So ProBalance acts as a bit of a safety in case the system, or some other application, needs to get a few CPU cycles to remain responsive but otherwise wouldn’t have been to.
Practically speaking, if you want to try additional tuning you will need to experiment with changes to see if you find some that work better for you.
Please see this page for a complete description of all system tray icons.
See this link for all Process Lasso features.
That said, we do offer:
CPUBalance – is a simpler rendition of Process Lasso focused on ProBalance only.
The ProBalance algorithm is designed in such a way that it will never degrade your system performance, only improve it.
It is extremely conservative. For instance, one of it’s many criteria (by default) is a process must be of normal priority class. Most audio apps set themselves to a High priority class. Thus, this exclusion was added, as it is assumed the application that sets it’s own priority class knows best.
Worst case if ProBalance did take action on some important process, you can always exclude it, but I very rarely hear of this due to the built-in exclusions and conservative nature.
Absolutely NOT. Do not do this. ProBalance will handle priority class adjustments that are necessary, if any are. Most of the time it will take no action since it is designed to be conservative and has numerous criteria that must be met before it ever makes a marginal, temporary change to a background process’s priority class.
Users should not try to rank processes in importance to them or make too many tweaks to process priority classes! You will do more harm than good.
Restricting memory consumption is problematic. If a process needs to go beyond some threshold in virtual memory consumption then your options are (a) to deny the allocation, certainly resulting in an unrecoverable exception in the application, or to (b) stall the application while you wait for some other condition to be met (like a reduction in total virtual memory use). Neither is a good option.
Of course you can ‘trim’ the virtual memory, but that isn’t going to be effective if the virtual memory is actively referenced, it will just get paged right back in as soon as it is referenced. This is normally never a good idea as Windows will page out unreferenced virtual memory anyway.
Process Lasso does offer another option, setting a Watchdog rule to restart (or just terminate) a process if it exceeds a virtual memory use threshold. That may be the best and most proper action in many cases.
First, let us be sure your expectations are correct – no product is a panacea for all system problems, and certainly not all use cases benefit equally from Process Lasso’s automated tuning. However, ProBalance does always keep you protected from that ‘worst case’ scenario, which you may encounter at some point, and it will save you from an improper shutdown.
ProBalance also does not act just to pretend to be doing something. It acts only when necessary. So if you are barely taxing your system, you aren’t going to see much difference in responsiveness. However, during times when you have your CPU loaded up, you will see a dramatic increase in responsiveness if the problem is CPU bound and ProBalance is able to cope with it. Sometimes the issue is I/O related, like waiting for a hard drive, but when it is CPU related, ProBalance addresses it.
This is well demonstrated by real-world and synthetic demos like our CPUEater Demo. I recommend that you read and try the CPUEater Demo yourself to see the impact. There is no trick here. You can recreate the demo in any language with a simple infinite loop (and nothing else!). See this page for more information on ProBalance …
Note that the Automation Features are ‘utility features’, so if you need them, then you need them. They don’t relate to this answer.
A single thread can’t be externally split into multiple threads, thus you can’t force use of unused CPU or GPU cores. You could force that single thread to be swapped between the CPU cores, but that would only decrease performance due to the switches, and have the same total CPU utilization.
The application has to be programmed to utilize multiple threads in order to make use of all cores. So you might say, “Ok, then why didn’t they do that?”. Well, some actions are linear in nature. In fact, many are. For instance, if I’m adding 2+2=4, it’s really hard to break that up into multiple threads.
The same goes for use of the GPU. The application has to be programmed to use it, you can’t force it to change it’s characteristics later.
This is why the performance of individual CPU cores still matters. If you have single-threaded CPU bound load, you can have 256 CPU cores, but only 1 will be utilized, and it’s individual performance will be the system max.
First, make sure they are enabled in the View menu (if Process Lasso). Second, make sure you have the right bit-size. This may require a product reinstall. Otherwise, your performance counters are in some way corrupted and there is little else that can be done. The command ‘lodctr.exe /r’ is run for you to try to repair this condition if Lasso finds it to be the case, so all that can be done is done.
Yes, if you have an active PC, you may want to disable certain Process Lasso log events like process creation/termination, or disable logging entirely. For a highly active PC or server, it can be resource consuming. Also remember that you do not need to have the GUI running all the time since the stand-alone core engine (processgovernor.exe) does everything that is important.
Process Lasso is great for games and other applications that need close to real-time performance.
Performance Mode (formerly Gaming Mode) configures ProBalance and the system power plan in such a way as to be best equipped to run games or other resource intensive applications.
For the most part, Performance Mode is simply the engagement of BHP (or other specified power plan). However, Performance Mode also interacts with other features that have options that disable or change their behavior when Performance Mode is engaged. Finally, Performance Mode creates a more simplified user experience. Certainly you can ignore Performance Mode and use the ‘application power profiles’.
Process Lasso’s Keep Awake works by issuing a power subsystem API call to inform the system that activity is still occurring. It does NOT do any ‘dirty hack’ like emulate keyboard input, as such is not necessary. It will issue this call once a minute at minimum, more if required.
No, it is not included, and yes, they are designed to run together.
Basically, ParkControl Pro has features not present in Process Lasso, such as a dynamically changing system tray icon that reflects core parking status. Going forward, there will be more differences.
They are designed to work along-side each other, so when ParkControl Pro is installed, Process Lasso’s ‘Core parking’ tool will actually just open ParkControl Pro’s window. This can lead to the perception that it is ‘within’ Process Lasso, but the only thing within Process Lasso is a more limited rendition of ParkControl (no Pro).
In some cases, yes, but it depends on your reason, and you need to be smart about it.
If your goal is increased performance, remember that the Windows OS CPU Scheduler tries to manage which threads are on what cores itself, and it’s not dumb. So, when you micro-manage CPU affinities, you are second-guessing it. This can only be appropriate when you are certain of what the loads are going to be and know what you’re doing.
If your goal is to limit CPU use, then you can do so by giving a problematic process access to only a limited subset of available cores. However, you must be sure that this process isn’t ‘blocking’, meaning slowing it doesn’t slow something else, or even everything else. Similarly, you obviously must be willing to tolerate the proportional decrease in that application’s performance.
We do NOT recommend limiting the CPU affinities of ALL processes with a broad rule like .; we also don’t recommend limiting the CPU affinity of system or security software.
In general, be conservative, cautious, selective, and smart!
There is no special setup, just install and go. I will note that we now have CPUBalance as well – which is ProBalance isolated from the other features. For many audio users, especially those who already have optimized PCs and don’t need all that Lasso offers, this may be the preferred solution. Read at https://bitsum.com/cpubalance/ .
Probably not. The best practice is to approach it from the other direction – lowering priority classes of anything that might interfere with your application(s).
Generally, you should simply let Process Lasso’s ProBalance dynamically lower the priority class of problematic background processes. You can also manually lower the priorities of processes that could interfere with your application.
This approach of lowering priorities is much more effective than raising the priority class of your desired application. In fact, setting a ‘High’ priority class normally doesn’t yield any advantage in performance.
It is also best to let ProBalance do it’s thing rather than make too many custom tweaks to prioity classes. Too many custom tweaks may cause complications.
Keep this in mind as well:
Some processes change their own CPU affinities, or are acted on by another application. In these cases, you need to turn on ‘Forced Mode’ at the bottom of the Options menu. This causes Process Lasso to continuously re-apply process rules. Without this setting, Process Lasso defers to whatever else is acting on the application.
No, they won’t conflict. You can use them together without complications since they do different things.
High DPI support was hacked onto Windows after-the-fact. Thus not all applications, including Process Lasso, are designed to take advantage of it. That means these apps must be scaled up to the higher DPI by the system. If they weren’t scaled, they would appear super tiny.
You can experiment with various scaling options, both for the system as a whole and per-application via the executable properties compatibility tab’s ‘Change high DPI settings’ button (see screenshot).
Whether these improve the appearance to your satisfaction depends on you. The default scaling behavior doesn’t bother me in the slightest on my high DPI displays.
Why don’t all apps just become High DPI aware? Because it is a ton of work, depending on the application. Process Lasso has graphs and a lot of custom drawing that all would need refactored. And Process Lasso, as a utility, isn’t something most people interact with so frequently that high DPI awareness is mission critical. Still, it is on the agenda.