Bitsum Community Forum

General Category => Process Lasso => Topic started by: Mickets on December 16, 2011, 03:35:54 PM

Title: Suspending / Changing Priority
Post by: Mickets on December 16, 2011, 03:35:54 PM
First of all: I admit that I haven't yet read the help file. Yes, I know that's bad. But I already copied it on to my phone to read on my way home...

I made a search and found a couple of topics here (http://bitsum.net/forum/index.php/topic,475.msg1997.html#msg1997) and here (http://bitsum.net/forum/index.php/topic,767.msg4699.html#msg4699), but couldn't exactly find the answer I needed.

So I'll bother you anyway with a question, because I need some quick advice.

I am used to using a bunch of software on my computer, and then for some reason I have to do something else. And instead of shutting down those programs that are processor-hungry, I'd simply suspend them via DTask Manager. This would avoid me spending time shutting down the applications, saving configurations, then reloading them etc.

It has always worked nicely (with the software I've used it on: some work software, Firefox, Thunderbird, etc).

Now, coming to Process Lasso, today I noticed that my computer was hanging up for minutes, several times in a row. It was driving me nuts. PL is running its default configuration, but I decided to fiddle around with those processes I mentioned before that are CPU hungry.

Questions:


I am using Windows XP SP3, PL Pro v5.1.0.21a

Thanks for any advice.

Michael
Title: Re: Suspending / Changing Priority
Post by: Jeremy Collake on December 16, 2011, 07:08:34 PM
Your habit of suspending processes is not a good one. It is an extremely unnatural state for a process to be in, and can cause complications. I would also advise *against* lowering the priorities of processes haphazardly.

In this case, the cause is uncertain, but could be related to excessive memory consumption by one or more processes. This would create an excessive amount of page faults (page in operations), which would require disk I/O, and that's likely where you'll find the bottleneck.

What is the total RAM utilization % as shown by Process Lasso? Can you also please confirm your version of Process Lasso again? I'm just making sure it is .21a and you did not mean .27a.