Joined: 9 Jan 02
I have a quad core processor that has recently (for the lase 3-4 days) stopped requesting Seti WUs. There have been no changes that I am aware of to my machine and I am still able to run two CUDA WUs concurrently. My preferences say to use all CPUs. If I do an Update, the activity log says that it is "not requesting new tasks".
I have run out of CPU WUs before, when the S@H website and servers are down for a few days, but whenever it came back up, it would fetch new tasks and resume. I am able to access the S@H site and there is no mention of a problem.
My SETI task is not suspended and it is set to request new tasks. Is this just a shortage of work units, or is there something else that is causing no new WUs? Anyone else seeing this?
Thanks in advance,
Joined: 27 May 07
This happens when you have several stuck uploads
(the exact number of stuck uploads that stop BOINC to ask for more tasks from a project depends on the number of CPUs (and GPUs?) you have.
The BOINC logic behind this: 'why ask for more tasks from a project that do not accept the results back?'
The upload problem is since a few days.
(You now have 'In progress (628)' tasks)
- ALF - "Find out what you don't do well ..... then don't do it!" :)
John McLeod VII
Joined: 15 Jul 99
Yes. 2 tasks that are not uploaded completely for each CPU or GPU in the system is the limit. This prevents a project that takes longer to transfer files than it takes to run from generating a (near) infinite set of work that needs to be uploaded.
There actually was a project that required a 100Mb/S link to avoid the problem. It also helps throttle work fetch for a project that is having trouble of some sort (bandwidth, slow upload server, ...) that may be temporary.
©2018 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.