Run Process Lasso as both a service at boot, and as a smaller process at login.

[Joseph Giedraitis]

My laptop is a piece of shit, and Process Lasso fixes almost all of its speed issues. But, the problem is, it doesn't always start up right away. So I'm stuck on a slow computer trying for several minutes just to get process lasso open. So, my idea on how to fix this is to run the core engine as a service at boot, as well as start up a lighter version as a program that will detect foreground processes. This program will then connect to the service in order to tell it what programs not to limit.

[edkiefer]

The default should load PL fast, I know on my system, I always see it right away for most part.
You can also set it to run as service but not sure how that affects startup speed in loading.

You probably would be best to just have governor running at startup, so save PL GUI when you need it after OS loads everything.

[Jeremy Collake]

This is something that I've considered before. What you're describing is having an agent running in the user session(s) that communicates to the service the active foreground process and any other sessions-specific information that the service doesn't have access to. It's not something I've implemented, but have thought about doing from time to time. At this time, I can't say when or if I'll actually implement it.

[Sean Dendle]

This is a feature that I too would be very interested in seeing.
+1 vote from me.

[Jeremy Collake]

I can confirm that such a per-session agent will be part of version 9.

[Sean Dendle]

That's great news. My team is looking forward to this feature.

[Jeremy Collake]

Indeed, this will be one the 'big name' improvements of v9, one of many. I wish I could just release tomorrow, but there are so many protocols and safeguards. It will not be long and will happen this year for sure though!