Had to stop using my v6 client for the opteron as it just want getting any work units. So now using v7 client and getting almost half the PPD.
Can you not specify which types of workunits to take by preference? I've not played around with it, but I thought it was possible via the advanced options.
List of performance by project/hardware: https://docs.google.com/spreadsheets/d/1vcVoSVtamcoGj5sFfvKF_XlvuviWWveJIg_iZ8U2bf0/pub?gid=2
List of advanced options: http://www.overclock.net/t/979691/info-v7-list-and-uses-of-advanced-options Not sure how up to date this is. I suspect however that the projects you were processing were V6 specific and have dried up, like the BIGADV projects. Wish they'd do some more projects like that again. It feels like there's been no initiatives from Stanford for ages, although that's probably more due to my ignorance.
I wasn't aware there was even any v6 work left to be done. I thought v6 had been dead for well over a year, since BIGADV was scrapped at the start of 2015. But I was out of the project fora couple of years and missed the whole v7 client launch, so it comes as no surprise that I didn't know the v6 clients would still get work.
Scorpuk - I switched my Opteron over to v7 after they ceased the BigAdv programme. What you need is BigAdv-type WU's on the Opteron, i.e. those that run the A5 core rather than the A4 core. In order to do that you need to add two 'extra slot options' (what used to be called 'flags'); (1) client-type=bigadv, and (2) max-packet-size=big The points won't be anywhere near BigAdv levels - those days are gone - but they will be at the full potential of your Opteron cores.
For general info: As far as I know the v6 client can still be used, i.e. it has not been deprecated yet. Obviously it is not being updated though. For general clarity: The v6 client doesn't do the Folding - that's done by the Cores - it just oversees the handling of Cores and WU's, and receiving/sending data/results.
Cheers Doc. I didn't know what flags to use in v7, so just kept running with v6 as it seemed to work ok. Well until now. Will probably be taking the opterons off over the next month as I move my media server to this case and expand the collection of drives. Can stick a 970 in there to get more PPD than the opterons.
That's the depressing thing for multi-socket machines - my GTX 960 has a greater PPD than my 48 Operton cores
Bleh. not getting anything either on client v7 with those settings Code: 18:27:57:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:27:57:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:27:57:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:27:58:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:27:58:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:27:58:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:27:59:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:27:59:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:28:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:28:00:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:28:59:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:29:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:29:00:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:29:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:29:00:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:29:16:WU01:FS00:0xa4:Completed 500000 out of 500000 steps (100%) 18:29:17:WU01:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000 18:29:27:WU01:FS00:0xa4: 18:29:27:WU01:FS00:0xa4:Finished Work Unit: 18:29:27:WU01:FS00:0xa4:- Reading up to 5429088 from \"01/wudata_01.trr\": Read 5429088 18:29:27:WU01:FS00:0xa4:trr file hash check passed. 18:29:27:WU01:FS00:0xa4:- Reading up to 5822260 from \"01/wudata_01.xtc\": Read 5822260 18:29:27:WU01:FS00:0xa4:xtc file hash check passed. 18:29:27:WU01:FS00:0xa4:edr file hash check passed. 18:29:27:WU01:FS00:0xa4:logfile size: 342163 18:29:27:WU01:FS00:0xa4:Leaving Run 18:29:30:WU01:FS00:0xa4:- Writing 11625915 bytes of core data to disk... 18:29:33:WU01:FS00:0xa4:Done: 11625403 -> 11019899 (compressed to 94.7 percent) 18:29:33:WU01:FS00:0xa4: ... Done. 18:29:34:WU01:FS00:0xa4:- Shutting down core 18:29:34:WU01:FS00:0xa4: 18:29:34:WU01:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT 18:29:35:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64) 18:29:35:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:7528 run:61 clone:0 gen:496 core:0xa4 unit:0x0000027bfbcb017d55990af7d2ef3105 18:29:35:WU01:FS00:Uploading 10.51MiB to 128.143.199.97 18:29:35:WU01:FS00:Connecting to 128.143.199.97:8080 18:29:41:WU01:FS00:Upload 26.17% 18:29:47:WU01:FS00:Upload 52.33% 18:29:53:WU01:FS00:Upload 76.12% 18:30:01:WU01:FS00:Upload complete 18:30:01:WU01:FS00:Server responded WORK_ACK (400) 18:30:01:WU01:FS00:Final credit estimate, 8731.00 points 18:30:01:WU01:FS00:Cleaning up 18:30:36:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:30:37:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:30:37:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:30:37:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:30:37:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:33:13:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:33:14:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:33:14:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:33:15:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:33:15:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:37:28:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:37:28:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:37:28:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:37:29:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:37:29:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:44:19:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:44:20:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:44:20:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:44:20:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:44:20:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 18:55:26:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m18:55:27:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 18:55:27:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m18:55:28:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m18:55:28:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 19:13:21:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m19:13:22:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 19:13:22:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m19:13:23:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m19:13:23:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 19:42:25:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m19:42:27:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 19:42:27:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m19:42:28:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m19:42:28:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m 20:29:23:WU00:FS00:Connecting to 171.67.108.45:8080 \x1b[93m20:29:23:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment\x1b[0m 20:29:23:WU00:FS00:Connecting to 171.67.108.204:80 \x1b[93m20:29:24:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment\x1b[0m \x1b[91m20:29:24:ERROR:WU00:FS00:Exception: Could not get an assignment\x1b[0m
I'm also getting the same issue now - it is possible there is an issue with the AS, or a shortage of A5-based WU's. Delete the CPU slot configuration and start a new one - that should reset the Folding Slot ID which should allow it to point to a different AS to at least get some work. Edit: Seems there's a shortage of WU's for multi-core (>24 core) machines; Folding Forum link.
Update: Looking on the official Folding Forum, though the v6 client should still be valid to use, not many of the servers are issuing work to this client any more, so the recommendation is to upgrade to the v7 client.
Thanks Doc, I knew this but I fell into the bad habit of writing about it incorrectly years ago and old habits die hard!
