Affinity changer is doing something...

[BinarySynapse]

I was getting about 22-23 minutes per frame on a Q6600. I installed AC and now I'm getting 17-18 minutes per frame. This is on Vista x64 SP1.

Log file from my second instance of FAH.

[00:59:21] Writing local files
[00:59:21] Completed 320000 out of 500000 steps (64 percent)
[01:22:28] Writing local files
[01:22:28] Completed 325000 out of 500000 steps (65 percent)
[01:45:14] Writing local files
[01:45:14] Completed 330000 out of 500000 steps (66 percent)
[02:03:10] Writing local files
[02:03:10] Completed 335000 out of 500000 steps (67 percent)
[02:21:03] Writing local files
[02:21:03] Completed 340000 out of 500000 steps (68 percent)

 

[APOLLO]

Affinity Changer is recommended if you have a single quad or C2D machine and running Windows SMP. Running the app will transform a Windows folder to near Linux production levels.

BTW, I wasn't going to post a new thread about this, but since we're discussing AC, I recently read on the F@H Support Forum that the author of the AC app is currently working on a dual quad version of the program. There aren't very many using 8-core systems but I thought I'd mention it.

 

[BinarySynapse]

Well, I read the SMP quide and Killer had mentioned extensive testing of AC which showed no benefit in Vista SP1. I've got a massive benefit, but it may be that my system isn't configured right to begin with.

 

[APOLLO]

I wasn't aware of AC issues in Vista. I don't have Vista on my folding machines only on my laptop. It's good to know you have it running effectively.

 

[Killer[MoB]]

It was with the SP1 that was leaked early. I hope they corrected the problems with SP1 before the final release.

 

[kazak]

So I just got a Q6600 but my frame rates are much lower than yours and I bumped it back down to stock speeds. I'm on Vista64 Ultimate w/ SP1. Won't be able to tell you what it was before AC since I never uninstalled it when I swapped CPU. Got 4GB DDR2-800 but that's all I can think of that might have anything to do with my frame rates.

Overnight...I think this is over night....nothing else running.

[06:19:00] Completed 260000 out of 500000 steps (52 percent)
[06:31:24] Writing local files
[06:31:24] Completed 265000 out of 500000 steps (53 percent)
[06:43:44] Writing local files
[06:43:44] Completed 270000 out of 500000 steps (54 percent)
[06:56:02] Writing local files
[06:56:02] Completed 275000 out of 500000 steps (55 percent)

During the day...bunch of apps running; iTunes, browsers, RDP to other machines, Office apps, Acrobat, etc.

[20:10:30] Writing local files
[20:10:30] Completed 30000 out of 500000 steps (6 percent)
[20:23:49] Writing local files
[20:23:49] Completed 35000 out of 500000 steps (7 percent)
[20:37:16] Writing local files
[20:37:16] Completed 40000 out of 500000 steps (8 percent)
[20:50:32] Writing local files
[20:50:32] Completed 45000 out of 500000 steps (9 percent)

 

[Tigerbiten]

At 3.1 Ghz my Linux clients inside the VM's are crunching p2605 at ~12:25 per frame.

[08:30:12] Writing local files
[08:30:12] Completed 260000 out of 500000 steps  (52 percent)
[08:42:30] Writing local files
[08:42:30] Completed 265000 out of 500000 steps  (53 percent)
[08:54:58] Writing local files
[08:54:58] Completed 270000 out of 500000 steps  (54 percent)
[09:07:13] Writing local files
[09:07:13] Completed 275000 out of 500000 steps  (55 percent)
[09:19:29] Writing local files
[09:19:29] Completed 280000 out of 500000 steps  (56 percent)
[09:31:57] Writing local files
[09:31:57] Completed 285000 out of 500000 steps  (57 percent)

Its always helpful to give the protien number so others can see what your crunching.

Luck ..........

 

[kazak]

Cool. That's a really good tip. In my case above, it's 2653

 

[BinarySynapse]

Sorry about that. I've been crunching nothing but 2653's on both machines since I started them up last week. Didn't think to include that information.