Changing geokilla007 to geokilla.
Posted: Fri Sep 12, 2008 4:26 pm
Hi guys. To keep things simple since I'm going to start and try to fold on multiple computers as well as friend's computers, I'm going to be folding under a new name. That name would be geokilla. Previously, I used geokilla007. I'll be generating more PPD now that I can fold on at least two computers.
Oh, and I believe I managed to get CPU and GPU clients to run simultaneously in Windows XP. Here's what I did.
Before, I was running the CPU and GPU client by itself and everything's fine. If I run them together, the CPU client would GREATLY slow down the GPU client, according to task manager. So then I have F@H do its affinity lock after I reinstalled F@H. Still no go if I ran both the CPU and GPU client together. So I went to Task Manager, and did the following:
F@H CPU (and anything related to CPU)> Set Affinity> Check only Core 0
F@H GPU (and anything related to GPU)> Set Affinity> Check only Core 1
I didn't restart the computer yet and let it run on its own as a service. At the moment, I have the programs running as command prompt.
Oh, and I did a "min-experiment". I had just the GPU client running, and it would complete 1% approximately every 2 to 3 minutes. Now that I changed the affinity and have them both running together, the GPU client takes 2 to 3 min to complete 1% while the CPU client takes about 5 min to complete 1%.
Just tried running the CPU client by itself, and it takes just a bit over 4 min to complete 1%. This is the same as when running both the CPU and GPU client together.
I'm going to restart the computer and let the clients run as a service. I'll use F@H to monitor how long it takes to complete each percent. If anything changes, I'll report it in this thread.
Edit: As soon as I restart the computer, I can't control the Affinity anymore. Guess it's only GPU client till I can find another way to deal with the core affinity problem.
Oh, and I believe I managed to get CPU and GPU clients to run simultaneously in Windows XP. Here's what I did.
Before, I was running the CPU and GPU client by itself and everything's fine. If I run them together, the CPU client would GREATLY slow down the GPU client, according to task manager. So then I have F@H do its affinity lock after I reinstalled F@H. Still no go if I ran both the CPU and GPU client together. So I went to Task Manager, and did the following:
F@H CPU (and anything related to CPU)> Set Affinity> Check only Core 0
F@H GPU (and anything related to GPU)> Set Affinity> Check only Core 1
I didn't restart the computer yet and let it run on its own as a service. At the moment, I have the programs running as command prompt.
Oh, and I did a "min-experiment". I had just the GPU client running, and it would complete 1% approximately every 2 to 3 minutes. Now that I changed the affinity and have them both running together, the GPU client takes 2 to 3 min to complete 1% while the CPU client takes about 5 min to complete 1%.
Just tried running the CPU client by itself, and it takes just a bit over 4 min to complete 1%. This is the same as when running both the CPU and GPU client together.
I'm going to restart the computer and let the clients run as a service. I'll use F@H to monitor how long it takes to complete each percent. If anything changes, I'll report it in this thread.
Edit: As soon as I restart the computer, I can't control the Affinity anymore. Guess it's only GPU client till I can find another way to deal with the core affinity problem.