Since my gloomy post a half day ago claiming to outline status of four different CPU work sources, others have clarified my inaccurate representation of the status of various work sources. I'll just observe here that at one time or another in the last twelve hours hosts of mine have received new work from all three of S6 CasA, FGRP4 (not resends, but another new beta test batch), and BRP4 (Arecibo).
Normally I test CPU applications for credit productivity and other suitability and choose just one for each host, as I don't like the way the scheduling stuff behaves with multiple applications, but for the time being I've enabled most of the CPU work source applications and set my queues to 2 day length, hoping to help the project by running whatever is available, and hoping the dry spells won't last longer than two days.
... for the time being I've enabled most of the CPU work source applications and set my queues to 2 day length, hoping to help the project by running whatever is available, and hoping the dry spells won't last longer than two days.
I didn't think your previous post was 'gloomy' or 'inaccurate' at all. I thought it was quite a decent summary of things as you saw them. It's very hard, from a distance, to guess what's going on 'behind the scenes'.
S6CasA primary tasks seem to be reducing by about 20K per day so there are several days worth of these still left. After that, there will be resends for quite a while. FGRP4 should kick in well before there is any real shortage. I'm sure the project will be grateful for any help in 'dealing with the dregs'. What can happen is that as soon as primary tasks finish for S6, people will tend to disable that run and enable what they want to do next, forgetting about all the resends still to come. So as general advice for those willing to help, don't disable S6CasA for at least another month or two. By that time the resends should be just about finished.
RE: Current EST is early
)
Thanks! Good luck with everything!
Cheers,
Gary.
Since my gloomy post a half
)
Since my gloomy post a half day ago claiming to outline status of four different CPU work sources, others have clarified my inaccurate representation of the status of various work sources. I'll just observe here that at one time or another in the last twelve hours hosts of mine have received new work from all three of S6 CasA, FGRP4 (not resends, but another new beta test batch), and BRP4 (Arecibo).
Normally I test CPU applications for credit productivity and other suitability and choose just one for each host, as I don't like the way the scheduling stuff behaves with multiple applications, but for the time being I've enabled most of the CPU work source applications and set my queues to 2 day length, hoping to help the project by running whatever is available, and hoping the dry spells won't last longer than two days.
RE: ... for the time being
)
I didn't think your previous post was 'gloomy' or 'inaccurate' at all. I thought it was quite a decent summary of things as you saw them. It's very hard, from a distance, to guess what's going on 'behind the scenes'.
S6CasA primary tasks seem to be reducing by about 20K per day so there are several days worth of these still left. After that, there will be resends for quite a while. FGRP4 should kick in well before there is any real shortage. I'm sure the project will be grateful for any help in 'dealing with the dregs'. What can happen is that as soon as primary tasks finish for S6, people will tend to disable that run and enable what they want to do next, forgetting about all the resends still to come. So as general advice for those willing to help, don't disable S6CasA for at least another month or two. By that time the resends should be just about finished.
Cheers,
Gary.