Message boards :
Number crunching :
Only getting GPU work units.
Message board moderation
Author | Message |
---|---|
MilVetRetired Send message Joined: 24 Apr 12 Posts: 16 Credit: 19,316,434 RAC: 4 |
Only getting GPU work units for some reason. Options are set correctly. Anyone seeing this too? |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Only getting GPU work units for some reason. Options are set correctly. Anyone seeing this too? See the OTHER thread about only getting GPU work units. It's only a couple threads down from yours. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Same here. I'm out of CPU work. |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Have you read the other thread yet? Here, I'll Link ya... "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Yep. Now I am on a Communication deferred for 01:46:33...... 10/11/2012 09:55:37 | SETI@home | [work_fetch] REC 502488.104 priority -0.000177 (project backoff 6409.85) 10/11/2012 09:55:37 | | [work_fetch] CPU: shortfall 2592000.00 nidle 4.00 saturated 0.00 busy 0.00 10/11/2012 09:55:37 | Milkyway@home | [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 09:55:37 | SETI@home | [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 09:55:37 | | [work_fetch] NVIDIA: shortfall 1210351.79 nidle 0.00 saturated 42346.83 busy 0.00 10/11/2012 09:55:37 | Milkyway@home | [work_fetch] NVIDIA: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 09:55:37 | SETI@home | [work_fetch] NVIDIA: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 09:55:37 | | [work_fetch] ------- end work fetch state ------- 10/11/2012 09:55:37 | | [work_fetch] No project chosen for work fetch Running BOINC 7.0.28 (x64) |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Yep. Well, you appear not to be asking for CPU work. So, you shall get none. CPU fetch share 0.000....... While the Nvidia shortfall is 1210351.79.... So that work request still appears to be seeking GPU work. Did you disable GPU in your Seti@home preferences and update? "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
Now I am on a Communication deferred for 01:46:33...... You probably know this, but that deferral can be reset by going NNT/Manual update/allow new tasks. Also resets the work fetch deferrals that you see on project properties if they have escalated due to unsuccessful fetches. Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Well, you appear not to be asking for CPU work. So, you shall get none. CPU fetch share 0.000....... Well I cant now find the setting. I can only find diable GPU while computer is in use. Sorry for the finnish. Boinc somehow puts the options in Finnish although I would actually prefer English. Suorittimen käyttö Hyllytä työ koneen ollessa akkukäytöllä? (koskee vain kannettavia) kyllä Hyllytä työ tietokoneen ollessa käytössä? ei Hyllytä näytönohjaimen (GPU) työ tietokoneen ollessa käytössä? versiosta 6.6.21+ ei "Käytössä" tarkoittaa hiiren/näppäimistön käyttöä 3 minuuttia Hyllytä työ jos hiirtä/näppäimistöä ei ole käytetty (tarvitaan joissakin koneissa mentäessä virransäästötilaan) --- minuuttia Suspend work when non-BOINC CPU usage is above 0 means no restriction Enforced by version 6.10.30+ 25% |
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
Well I cant now find the setting. I can only find diable GPU while computer is in use Website project preferences, in English "use Nvidia GPU" (or ATI). That doesn't block crunching what you have, just tells BOINC on the next update to stop asking for gpu work. Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Try this..... Go to your home account page. You should see...... SETI@home preferences. Click that. Should show you primary (default)preferences. If you have not selected any other venues......that's the one your rigs are working with. You should see 'use ATI GPU' yes or no. And 'use Nvidia GPU' yes or no. Click them to NO and the server will not attempt to send you more GPU work. GPU processing on the tasks you have on hand is not affected. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
No help with just suspending GPU activity. 10/11/2012 10:48:22 | | [cpu_sched] suspending GPU activity 10/11/2012 10:48:22 | SETI@home | [cpu_sched] Preempting 27se12ab.14845.5793.140733193388044.10.36_0 (removed from memory) 10/11/2012 10:48:22 | SETI@home | [cpu_sched] Preempting 27se12ab.14845.5793.140733193388044.10.55_0 (removed from memory) 10/11/2012 10:48:22 | SETI@home | [cpu_sched] Preempting 27se12ab.14845.5793.140733193388044.10.27_1 (removed from memory) 10/11/2012 10:48:22 | SETI@home | [cpu_sched] Preempting 27se12ab.15181.4566.140733193388045.10.218_1 (removed from memory) 10/11/2012 10:48:22 | SETI@home | [cpu_sched] Preempting 27se12ab.14845.5793.140733193388044.10.48_1 (removed from memory) 10/11/2012 10:48:22 | SETI@home | [cpu_sched] Preempting 27se12ab.14845.5793.140733193388044.10.83_0 (removed from memory) 10/11/2012 10:48:24 | | [work_fetch] Request work fetch: application exited 10/11/2012 10:48:24 | | [work_fetch] Request work fetch: application exited 10/11/2012 10:48:24 | | [work_fetch] Request work fetch: application exited 10/11/2012 10:48:24 | | [work_fetch] Request work fetch: application exited 10/11/2012 10:48:24 | | [work_fetch] Request work fetch: application exited 10/11/2012 10:48:26 | | [work_fetch] Request work fetch: application exited 10/11/2012 10:48:27 | | [work_fetch] work fetch start 10/11/2012 10:48:27 | | [work_fetch] ------- start work fetch state ------- 10/11/2012 10:48:27 | | [work_fetch] target work buffer: 604800.00 + 43200.00 sec 10/11/2012 10:48:27 | Milkyway@home | [work_fetch] REC 0.000 priority 0.000000 (no new tasks) 10/11/2012 10:48:27 | SETI@home | [work_fetch] REC 502240.392 priority -0.000168 (project backoff 3239.49) 10/11/2012 10:48:27 | | [work_fetch] CPU: shortfall 2592000.00 nidle 4.00 saturated 0.00 busy 0.00 10/11/2012 10:48:27 | Milkyway@home | [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:27 | SETI@home | [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:27 | | [work_fetch] NVIDIA: shortfall 1214294.56 nidle 0.00 saturated 40257.60 busy 0.00 10/11/2012 10:48:27 | Milkyway@home | [work_fetch] NVIDIA: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:27 | SETI@home | [work_fetch] NVIDIA: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:27 | | [work_fetch] ------- end work fetch state ------- 10/11/2012 10:48:27 | | [work_fetch] No project chosen for work fetch 10/11/2012 10:48:36 | SETI@home | update requested by user 10/11/2012 10:48:36 | | [work_fetch] Request work fetch: project updated by user 10/11/2012 10:48:37 | | [work_fetch] work fetch start 10/11/2012 10:48:37 | | [work_fetch] set_request(): ninst 4 nused_total 9.240000 nidle_now 4.000000 fetch share 1.000000 req_inst 4.000000 10/11/2012 10:48:37 | | [work_fetch] set_request(): ninst 2 nused_total 76.230000 nidle_now 0.000000 fetch share 1.000000 req_inst 0.000000 10/11/2012 10:48:37 | | [work_fetch] ------- start work fetch state ------- 10/11/2012 10:48:37 | | [work_fetch] target work buffer: 604800.00 + 43200.00 sec 10/11/2012 10:48:37 | Milkyway@home | [work_fetch] REC 0.000 priority -0.000000 (no new tasks) 10/11/2012 10:48:37 | SETI@home | [work_fetch] REC 502240.392 priority -1.000168 10/11/2012 10:48:37 | | [work_fetch] CPU: shortfall 2592000.00 nidle 4.00 saturated 0.00 busy 0.00 10/11/2012 10:48:37 | Milkyway@home | [work_fetch] CPU: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:37 | SETI@home | [work_fetch] CPU: fetch share 1.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:37 | | [work_fetch] NVIDIA: shortfall 1214293.55 nidle 0.00 saturated 40258.10 busy 0.00 10/11/2012 10:48:37 | Milkyway@home | [work_fetch] NVIDIA: fetch share 0.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:37 | SETI@home | [work_fetch] NVIDIA: fetch share 1.000 rsc backoff (dt 0.00, inc 0.00) 10/11/2012 10:48:37 | | [work_fetch] ------- end work fetch state ------- 10/11/2012 10:48:37 | SETI@home | [sched_op] Starting scheduler request 10/11/2012 10:48:37 | SETI@home | [work_fetch] request: CPU (2592000.00 sec, 4.00 inst) NVIDIA (1214293.55 sec, 0.00 inst) 10/11/2012 10:48:37 | SETI@home | Sending scheduler request: Requested by user. 10/11/2012 10:48:37 | SETI@home | Reporting 704 completed tasks, requesting new tasks for CPU and NVIDIA 10/11/2012 10:48:37 | SETI@home | [sched_op] CPU work request: 2592000.00 seconds; 4.00 devices 10/11/2012 10:48:37 | SETI@home | [sched_op] NVIDIA work request: 1214293.55 seconds; 0.00 devices |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Yep. This was what I was looking for. Seti scheduler times out when it has problem with confirming the 700 + tasks.. Lets see how the update goes this time. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Here is the update: - no progress.....:(.. 10/11/2012 11:00:22 | SETI@home | [sched_op] Starting scheduler request 10/11/2012 11:00:22 | SETI@home | [work_fetch] request: CPU (2592000.00 sec, 4.00 inst) NVIDIA (1214228.00 sec, 0.00 inst) 10/11/2012 11:00:22 | SETI@home | Sending scheduler request: Requested by user. 10/11/2012 11:00:22 | SETI@home | Reporting 704 completed tasks, requesting new tasks for CPU and NVIDIA 10/11/2012 11:00:22 | SETI@home | [sched_op] CPU work request: 2592000.00 seconds; 4.00 devices 10/11/2012 11:00:22 | SETI@home | [sched_op] NVIDIA work request: 1214228.00 seconds; 0.00 devices 10/11/2012 11:03:10 | SETI@home | Scheduler request failed: Timeout was reached 10/11/2012 11:03:10 | SETI@home | [sched_op] Deferring communication for 3 hr 27 min 18 sec 10/11/2012 11:03:10 | SETI@home | [sched_op] Reason: Scheduler request failed 10/11/2012 11:03:10 | | [work_fetch] Request work fetch: RPC complete 10/11/2012 11:03:13 | | Project communication failed: attempting access to reference site 10/11/2012 11:03:15 | | Internet access OK - project servers may be temporarily down. 10/11/2012 11:03:16 | | [work_fetch] work fetch start 10/11/2012 11:03:16 | | [work_fetch] ------- start work fetch state ------- 10/11/2012 11:03:16 | | [work_fetch] target work buffer: 604800.00 + 43200.00 sec |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Yep. This was what I was looking for. There is a fix to limit the reported tasks to 100 at a time. It seems to help when the servers are tied in knots. I have it in place on all my rigs. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
Go NNT to work down the unreported tasks. You don't have to wait the 5 minutes when on NNT. The option Kittyman mentioned is <max_tasks_reported>50</max_tasks_reported> din the options section of cc_config.xml. You may want to try 100 instead of 50. Max accepted is now 256 per a recent post. The less you try, the better the probability - but you have a lot more than I have to deal with. Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Ok. Changed the max reported results to 100. I recall Richard H. mentioned that newer Boinc versions had some kind of automatic fix not to send too many results, go figure. 10/11/2012 11:15:37 | SETI@home | [sched_op] Starting scheduler request 10/11/2012 11:15:37 | SETI@home | [work_fetch] request: CPU (2592000.00 sec, 4.00 inst) NVIDIA (1214768.09 sec, 0.00 inst) 10/11/2012 11:15:37 | SETI@home | Sending scheduler request: To report completed tasks. 10/11/2012 11:15:37 | SETI@home | Reporting 100 completed tasks, requesting new tasks for CPU and NVIDIA 10/11/2012 11:15:37 | SETI@home | [sched_op] CPU work request: 2592000.00 seconds; 4.00 devices 10/11/2012 11:15:37 | SETI@home | [sched_op] NVIDIA work request: 1214768.09 seconds; 0.00 devices |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Seems now to at least accept the report: 10/11/2012 11:15:37 | SETI@home | [sched_op] Starting scheduler request 10/11/2012 11:15:37 | SETI@home | [work_fetch] request: CPU (2592000.00 sec, 4.00 inst) NVIDIA (1214768.09 sec, 0.00 inst) 10/11/2012 11:15:37 | SETI@home | Sending scheduler request: To report completed tasks. 10/11/2012 11:15:37 | SETI@home | Reporting 100 completed tasks, requesting new tasks for CPU and NVIDIA 10/11/2012 11:15:37 | SETI@home | [sched_op] CPU work request: 2592000.00 seconds; 4.00 devices 10/11/2012 11:15:37 | SETI@home | [sched_op] NVIDIA work request: 1214768.09 seconds; 0.00 devices ------------ The 100 acknowledgements.... --------------- 10/11/2012 11:16:05 | SETI@home | [sched_op] handle_scheduler_reply(): got ack for task 30se12ab.24405.6202.140733193388048.10.105_2 10/11/2012 11:16:05 | SETI@home | [work_fetch] backing off CPU 572 sec 10/11/2012 11:16:05 | SETI@home | [work_fetch] backing off NVIDIA 330 sec 10/11/2012 11:16:05 | SETI@home | [sched_op] Deferring communication for 5 min 3 sec 10/11/2012 11:16:05 | SETI@home | [sched_op] Reason: requested by project 10/11/2012 11:16:05 | | [work_fetch] Request work fetch: RPC complete |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
Allowing the update with No New Tasks was news to me. Thanks for the tip. -Mark |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Allowing the update with No New Tasks was news to me. Thanks for the tip. I do it with the new tasks report included, and works...... But, things are rather hit and miss these days. I have, at least as the servers think, about 44,000 tasks in cache. Distributed across 9 rigs. Have no clue how many of those are on board or are ghosts. Rigs are all still crunching hard and reporting on a regular basis. I know they are all begging the servers for more kibbles, and getting denied every time. Due to the darn limits now imposed. No new work as far as I can tell since the 5th. But the server requests are still reporting the work. Look, I got 9 rigs burning here....... I cannot mind meld with them all. I have to trust that the project will give them something to do, or I will shut them off to save the electric bill. I still see over 43,000 tasks in play.......if ghosts are not a factor. Which I cannot verify. So far, the kitties have kibble. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Mark Lybeck Send message Joined: 9 Aug 99 Posts: 245 Credit: 216,677,290 RAC: 173 |
My other rig aint doing too good either: 10/11/2012 20:47:18 SETI@home Sending scheduler request: To fetch work. 10/11/2012 20:47:18 SETI@home Reporting 4 completed tasks, requesting new tasks for CPU and GPU 10/11/2012 20:48:59 SETI@home Computation for task 09se12ad.27942.9065.140733193388042.10.108_1 finished 10/11/2012 20:48:59 SETI@home Computation for task 09se12ad.27942.9065.140733193388042.10.107_1 finished 10/11/2012 20:48:59 SETI@home Starting 09se12ad.27942.9065.140733193388042.10.105_1 10/11/2012 20:48:59 SETI@home Starting task 09se12ad.27942.9065.140733193388042.10.105_1 using setiathome_enhanced version 610 10/11/2012 20:48:59 SETI@home Starting 09se12ad.27942.9065.140733193388042.10.104_1 10/11/2012 20:48:59 SETI@home Starting task 09se12ad.27942.9065.140733193388042.10.104_1 using setiathome_enhanced version 610 10/11/2012 20:49:01 SETI@home Started upload of 09se12ad.27942.9065.140733193388042.10.107_1_0 10/11/2012 20:49:01 SETI@home Started upload of 09se12ad.27942.9065.140733193388042.10.108_1_0 10/11/2012 20:49:12 SETI@home Scheduler request completed: got 0 new tasks 10/11/2012 20:49:12 SETI@home Message from server: No tasks sent 10/11/2012 20:49:12 SETI@home Message from server: No tasks are available for SETI@home Enhanced 10/11/2012 20:49:12 SETI@home Message from server: No tasks are available for Astropulse v505 10/11/2012 20:49:12 SETI@home Message from server: Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them 10/11/2012 20:49:12 SETI@home Message from server: This computer has reached a limit on tasks in progress 10/11/2012 20:49:12 SETI@home Message from server: Project has no tasks available 10/11/2012 20:49:15 SETI@home Finished upload of 09se12ad.27942.9065.140733193388042.10.107_1_0 10/11/2012 20:49:22 SETI@home Finished upload of 09se12ad.27942.9065.140733193388042.10.108_1_0 What does it mean that This computer has reached a limit on tasks in progress? All tasks are reported. |
©2024 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.