Whoa, console version really slowed down my box!

[ghost]

When I was using the Windows GUI version of the Folding program, I was able to move about and surf, etc., with no slowdown.

Now I'm using the console version and running 2x processes and my box is super slow when surfing.

How do I stop the console progs other than terminating the processes?

Thanks.

[Tawcan]

Do you have the priority set at idle? (During set up).

I have mine set at low and I have yet to experience any slow down... :nope:

How much ram is on your machine?

[ghost]

Originally posted by Tawcan
Do you have the priority set at idle? (During set up).

I have mine set at low and I have yet to experience any slow down... :nope:

How much ram is on your machine?

I'm not sure what I set the priority at during setup. How can I check? Remember this is the console version.

I'm running 1GB DDR400 RAM.

[Tawcan]

For mine on the client.cfg (open it with notepad) it says priority=96.... that's low priority though... Not sure what idle is.

Not 100% sure on this...maybe someone else can help you on this. :)

[ghost]

Originally posted by Tawcan
For mine on the client.cfg (open it with notepad) it says priority=96.... that's low priority though... Not sure what idle is.

Not 100% sure on this...maybe someone else can help you on this. :)

I don't have anything set with the first instance of the console program, but the second one has Priority=0 CPU / Usage=100.

[Tawcan]

Originally posted by ghost
I don't have anything set with the first instance of the console program, but the second one has Priority=0 CPU / Usage=100.

That looks right... maybe try setting up the 1st instance again...

[YeOldeStonecat]

Shouldn't slow down your box at all. You running a P4C? (I'm guessing so since you are running 2 consoles).

Default setup of the client should work fine for you...that's what I've done for years on..geeze, well over a hundred rigs over the past bit I've been folding.

My main rig at home I'm running 2x...I kill 1 while gaming, leave the other running. But I know I've gamed with both running, and still not had problems.

I haven't seen a console take more than 20 megs of RAM...usually in the low teens...if that. Right now I have one at 7 megs, another at 14 megs.

Again, try just running with the default settings...except that last switch which lets you have machine ID 1 and 2. You keep them in separate directories, right?

[ghost]

Originally posted by YeOldeStonecat
Shouldn't slow down your box at all. You running a P4C? (I'm guessing so since you are running 2 consoles).

Default setup of the client should work fine for you...that's what I've done for years on..geeze, well over a hundred rigs over the past bit I've been folding.

My main rig at home I'm running 2x...I kill 1 while gaming, leave the other running. But I know I've gamed with both running, and still not had problems.

I haven't seen a console take more than 20 megs of RAM...usually in the low teens...if that. Right now I have one at 7 megs, another at 14 megs.

Again, try just running with the default settings...except that last switch which lets you have machine ID 1 and 2. You keep them in separate directories, right?

Yeah, it's a P4c.

The box seems to be running fine now, it was strange how slow it was for a while last night. I associated the slowdown with running the consoles because it slowed shortly after initializing them. Now they're still running and everything is fine.

Each console has it's own directory and the ID's are set 1 and 2.

I'll keep an eye on it but thanks for your suggestions YOSC and Tawcan. ;)

[rickoic]

If you check the times on a work unit it will sometimes do that. Something was found in a frame or series of frames that will take longer than normal.

Or, you may have defrag, clean, or something like that scheduled to run once in awhile.

Tks
Rick

[ghost]

Originally posted by rickoic
If you check the times on a work unit it will sometimes do that. Something was found in a frame or series of frames that will take longer than normal.

Or, you may have defrag, clean, or something like that scheduled to run once in awhile.

Tks
Rick

Thanks for the reply, rickoic, but I'm not sure what you mean by that first paragraph.

[rickoic]

If you look at the FAHlog file, or if you have it folding on the task bar, check the times along the left side. The time from finishing a frame are there. The time between each frame is normally pretty close to the same from frame to frame. But sometimes the work unit runs into something that takes longer, or shorter, times and this may have happened to you.

Tks
Rick

[ghost]

Originally posted by rickoic
If you look at the FAHlog file, or if you have it folding on the task bar, check the times along the left side. The time from finishing a frame are there. The time between each frame is normally pretty close to the same from frame to frame. But sometimes the work unit runs into something that takes longer, or shorter, times and this may have happened to you.

Tks
Rick

Thanks for the clarification. ;)

The Folding consoles were kicking butt last night, it was the rest of my comp that seemed slow. Now everything is working normally.

I hate rebooting because I have to close the consoles first and I don't like interrupting the Folding! Am I getting infected with the Folding Bug or what? Is this normal? :D

[rickoic]

Folding IS very adictive. Gets so that you hate to HAVE to do anything on your pc that might take even 1 cpu cycle away from folding.

But we sometimes do. Seems like most of the time folding will release cpu cycles to let you do what you want without being noticed. But there seems to be certain times that it's a little reluctant to do so and you will notice a slow down, doesn't happen often enough for me to worry about it though.

And if you need to play a game and folding slows it down, DON'T PLAY!!!!!!! FOLD ON

Tks
Rick