I have 2 issues with process lasso. Now i don’t know if they are important for you but here is why i personal don’t like PRocess lasso
1: Process Lasso is very wasteful with resources. it has lot of bell and whistles that i find unneded
i ran this little test a whiel ago when i figure out how to drop the timed loop monitoring that eats UP CPU power
Work set Commit size CPU usage (Monitoring)
Mercury 220.127.116.11 588-616k 3336-3336k 0%
TopWinPrio 1 8276-11176k 29328-32228k 0.018%
TipWinPrio B3 6880-9792k 47776-50268k 0.024%
ProcessTamer 2400-2600k 3136-3416k 0.05%
ProcessLAsso 2108k 11748k 0.156%
Copy paste to notepad would make it easier to read
But what we see is that is that project mercury uses a lot less physical RAM (work set) and np CPU ressoruce When you are just sitting in the same programs (aka playing a game) but process lasso eats up 0.15% of the CPU constantly (i7 2700k @4.4 at the time)
You will also notice that almost every other release it for CPU usage optimizing, because I am constantly aware of not wasting the user resources.
2: in standard configuration Process lasso will fall flat under heavy multitasking. Try to run 3 HYperpi in the background to simulate heavy workload and run a benchmark you will see Process lasso does not help anywhere
The reason for this is that process lasso looks fro a process that uses up more than 80% of a core.
now if you have 8 process that are CPU heavy on a Quadcore CPU they are all only getting 50% each.
Process lasso does not find a single process taking more than 80% and therefore does not adjust anything
That is why Bitsum always tries to make you test with Their own progam to hide this issues from you and to have control of the test.
I always suggest using something that is not from my hand to test with.
However. if this applies to you are not are totally up to you. I am just giving in my 2 cents.
Personally i often have several CPU heavy process running because i do a lot of brute force compression. Which is the reason i made this program (inspired from topwinprio. but topwinprio had memory leaks)