V6 SMP client problem

[Kittyhawk]

It has been unable to get any work. What is wrong?
The following gets displayed:

Code: Select all

...
[13:26:05] + Attempting to get work packet
[13:26:05] - Connecting to assignment server
[13:26:06] + No appropriate work server was available; will try again in a bit.
[13:26:06] + Couldn't get work instructions.
[13:26:06] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[13:26:18] + Attempting to get work packet
[13:26:19] - Connecting to assignment server
[13:26:20] + No appropriate work server was available; will try again in a bit.
[13:26:20] + Couldn't get work instructions.
[13:26:20] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
...

[toTOW]

I'm not sure there are still work for v6 SMP clients ... I updated to v7 the last one I had months ago because it was too hard for it to get work ...

[bruce]

There may be intermittent periods of WU shortages / assignments. Upgrading to V7 is a good idea.

The projects that V6 can run will continue to gradually decrease in number over time.

[Nathan_P]

v6 probably only really works with the large core a5 wu, I haven't seen an SMP unit on Linux for weeks now and I haven't had time to test either v7 on this distro or keep trying v6 SMP

[Kittyhawk]

I didn't know there were limits as to which projects V6 could do.
Looks like I'll carry on using V7 for SMP folding.

After the V6 SMP client couldn't get new work, I tried Boinc Rosetta@Home for a few days, then tried Folding@Home V7.
From my experience so far, the RAM requirements for the latter are so much smaller.
~700MB per Rosetta@Home thread versus less than 100MB for SMP folding on 2 cores.

[Nathan_P]

Its not a question of limits, v6 can handle all the cpu cores, it struggles on the GPU cores as AFAIK it only works upto core 17.. The problem is the work server software has been upgraded and it doesn't like the v6 client for some reason.

[7im]

Newer servers that support newer features for error reporting and such, that are not supported in the older client, have a Minimum Client Version setting. Most newer servers have a Min Ver setting of 7.0 or higher to prevent any compatibility issues. So newer projects tend to run on V7 client only, while older projects can run on both v6 and V7 clients. But as older projects are completed, no new projects with v6 support are added. Only new projects with V7 support. So the projects (and their work units) will diminish over time as already noted. The v6 client will eventually be deprecated by eventual attrition.

[bruce]

... as older projects are completed, no new projects with v6 support are added

False.

From time to time, Kasson adds new projects designed to use FahCore_a5 on V6 and to support Kraken.