Just thought it would be interesting to know how long everyone keeps their computer on each day.

My computers ususally on for about 12 hours a day as i leaveit on when i go to uni and work, so folding at home does a fair bit.

You know precisely how long I leave mine running, Authur!

And what happened to never posting on the site again?

Anyways, for the benefit of this thread, the length of time I have it run for varies really, depending on if my sister goes on the computer or not - she always turns it off.

I've "only" had folding@home running for 5 hours today, although I had it running all yesterday and the day before.

So that means my current range is anything between 5 and 24 hours a day.

Weekdays: 6-7 hours
Weekends: 10-16 hours

24 - 7

it stays on all the time and on a 45 minute battery back.

Valcoren - are you folding for BOTF2 and if so what's your username on it?

yeah I fold for fold for botf2. im aurthur_wonderbird! (I started as gareth morgan though)

Dual Athlon 2400+ MP system: 24-7
Athlon X2 3800+ @2.6ghz system: about 19-20hrs avg / day (due to actually using it)

Computers are never physically off, except for a fast reboot..

I just started running it again, and I've just been letting it run continuously. I've got a dual-core Athlon X2 4200+, so it can run happily on one core without interfering with my work .

mstrobel; I've got a X2 3800+ (@2.6ghz, wahoo), and I have a console version running on both. I'll admit that sometimes Windows task scheduler is inefficient in that if you're running, say, a game and a file compression job at the same time, instead of pushing aside both F@H clients on both cores to do both jobs at full speed, it'll do something stupid and push aside only one F@H client and split one core to do both of your heavy-duty jobs on one core. In those cases, I notice it, and I have two .bat files on my desktop to quickly start and stop the services when I know I'm going to need both cores totally available.

But thats rare. During the 99% of the time I'm not using multithreaded apps or not doing serious multitasking, I don't even feel that F@H is running.

Might want to look in to it, that extra core could yield an extra 200 points per day easy.

And for anyone interested, the bat files look like this, just change where they point to accordingly:

FAHStart.bat
net start "FAH@C:+Program Files (x86)+Folding+FAH1+FAH504-Console.exe"
net start "FAH@C:+Program Files (x86)+Folding+FAH2+FAH504-Console.exe"

FAHStop.bat
net stop "FAH@C:+Program Files (x86)+Folding+FAH1+FAH504-Console.exe"
net stop "FAH@C:+Program Files (x86)+Folding+FAH2+FAH504-Console.exe"

Where the part in " " point to the service that was installed by the Console client upon configuration. Have to use the console for multi-cpu or multi-core, cause the graphic version tends to get in hissy fits, or at least used to.

In theory, I bet you could use graphical on one, console on the other. Let the console run forever, and when you want to free up the other core, then tell the graphical one on your sys tray to shut down. Just don't forget the -local flags for both console and graphical.

Well I haven't got a clue what any of that stuff means, Ringold.

You know more about my computer than me though. Will it help me in any way?

Anyone tried running 2 folding at home clients simultaniously on a single core system (ie Athlon XP or Pentium 4 Skt 478)? I know you can do it. As i've got two HDD's i was thinking of running it at the same time from my C and D drives. Any comments?

Dont try it, Trekboy. They'll be fighting for the same cache and access to RAM, so it'll degrade performance all around, for you the end user and for the clients.

Unless you've got a hyperthreading p4, in which case, with good RAM (512 or more), you might eek out a slight boost in ppd, at the cost of extra ram being consumed.

Also, HD doesn't matter much, it initially loads in to RAM and then records its progress about once every 15min (or if you have a console, however long a period as you select). Just can't be in the same folder, and with more than one running, -local flags need to be called either on the service entry or on the shortcut you use to launch it. Otherwise, they start fighting for registry access, if I understand what the -local flag does exactly.. I just know running without it with multiple clients causes problems.