The assign servers are assigning CPU clients to 128.252.203.9 and 206.223.170.146, both of which have no public jobs available at the moment. (They are in Accept status). Other WS do have CPU jobs available.
Is this a problem with the assign servers, or just an artefact of few CPU jobs being available in the whole system?
Edit: I asked the F@H Discord about it - the devs are being notified.
CPU clients assigned to WS without work
Moderators: Site Moderators, FAHC Science Team
CPU clients assigned to WS without work
Online: GTX 1660 Super + occasional CPU folding in the cold.
Offline: Radeon HD 7770, GTX 1050 Ti 4G OC, RX580
-
Joe_H
- Site Admin
- Posts: 8078
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: CPU clients assigned to WS without work
Probably just an artifact of there being just a few jobs left on those two servers, 128.252.203.9 and 206.223.170.146, and a limited number of WUs on other servers.
What can happen is that some WUs come in, the next Gen WU for each is generated and the two AS get an update that WUs are available to assign. These updates are periodic, not in realtime. So WU requests that match get directed to these Work Servers and those in the tail end of the queue can find there is none left before the AS gets an update listing no WUs available.
This condition should improve a bit in a few days, there are a few CPU projects in Beta that should be released to everyone soon.
What can happen is that some WUs come in, the next Gen WU for each is generated and the two AS get an update that WUs are available to assign. These updates are periodic, not in realtime. So WU requests that match get directed to these Work Servers and those in the tail end of the queue can find there is none left before the AS gets an update listing no WUs available.
This condition should improve a bit in a few days, there are a few CPU projects in Beta that should be released to everyone soon.