2684 vs 2684

[hspeirs]

Ok, so I have three machines running 6.34, One is running 6901 on A5 quite happily, the other two are running 2686's - but one as an A3, the other as an A5.

Anyone have an idea why ?

H.

 

[Activate: AMD]

maybe just a late A3 WU assignment from the server? I don't know how the assignment things work exactly, so I may be completely off base.

 

[hspeirs]

Activate - about 10 hours apart.Was a Damn moment.

 

[Patriot]

those wu can run under either core... its just a matter of when it was assigned...

 

[amdgamer]

Out of curiosity, has anyone gotten a 2684 yet under the new v6.34 client? I just made the switch for folding2 today after the A3 bigadv it was working on completed. I'll make the switch for folding1 tomarrow when it finished the 6900 A3.

 

[KMac]

Out of curiosity, has anyone gotten a 2684 yet under the new v6.34 client?

No 2684 (*knock on wood), but I currently have two 2686's running on A5 v6.34.

 

[APOLLO]

Out of curiosity, has anyone gotten a 2684 yet under the new v6.34 client?

Not yet but I only switched over two clients. I'm sure it will happen. I haven't heard anything about the P2684 project being completed or terminated. I'll post here if I see one.

 

[gkanakis]

Out of curiosity, has anyone gotten a 2684 yet under the new v6.34 client?

And I will be the first...

[10:09:33] Core required: FahCore_a5.exe
[10:09:33] Core found.
[10:09:33] Working on queue slot 01 [March 3 10:09:33 UTC]
[10:09:33] + Working ...
[10:09:33] - Calling '.\FahCore_a5.exe -dir work/ -nice 19 -suffix 01 -np 8 -nocpulock -checkpoint 3 -forceasm -verbose -lifeline 2836 -version 634'

[10:09:33]
[10:09:33] *------------------------------*
[10:09:33] Folding@Home Gromacs SMP Core
[10:09:33] Version 2.27 (Mar 12, 2010)
[10:09:33]
[10:09:33] Preparing to commence simulation
[10:09:33] - Assembly optimizations manually forced on.
[10:09:33] - Not checking prior termination.
[10:09:37] - Expanded 24824825 -> 30791309 (decompressed 124.0 percent)
[10:09:37] Called DecompressByteArray: compressed_data_size=24824825 data_size=30791309, decompressed_data_size=30791309 diff=0
[10:09:38] - Digital signature verified
[10:09:38]
[10:09:38] Project: 2684 (Run 0, Clone 2, Gen 71)

 

[SazanEyes]

I've got a P6900 running as A5. Looks like all the old WUs have been switched over. This explains why they were able to move to the new client so quickly.

 

[amdgamer]

And I will be the first...

[10:09:33] Core required: FahCore_a5.exe
[10:09:33] Core found.
[10:09:33] Working on queue slot 01 [March 3 10:09:33 UTC]
[10:09:33] + Working ...
[10:09:33] - Calling '.\FahCore_a5.exe -dir work/ -nice 19 -suffix 01 -np 8 -nocpulock -checkpoint 3 -forceasm -verbose -lifeline 2836 -version 634'

[10:09:33]
[10:09:33] *------------------------------*
[10:09:33] Folding@Home Gromacs SMP Core
[10:09:33] Version 2.27 (Mar 12, 2010)
[10:09:33]
[10:09:33] Preparing to commence simulation
[10:09:33] - Assembly optimizations manually forced on.
[10:09:33] - Not checking prior termination.
[10:09:37] - Expanded 24824825 -> 30791309 (decompressed 124.0 percent)
[10:09:37] Called DecompressByteArray: compressed_data_size=24824825 data_size=30791309, decompressed_data_size=30791309 diff=0
[10:09:38] - Digital signature verified
[10:09:38]
[10:09:38] Project: 2684 (Run 0, Clone 2, Gen 71)

I guess the slow TPF's are still the same with the 2684's on the A5 core? TPF's don't appear to have changed at all for any of the old A3 WU's, although we didn't really expect them to.

 

[SatTech]

My SR-2 just finished up a 2684 on the new 6.34 client. Same TPFs as ever, same crappy PPD.