Advanced search

Message boards : Number crunching : strange notification in event log

Author Message
Erich56
Send message
Joined: 1 Jan 15
Posts: 1090
Credit: 6,603,906,926
RAC: 18,783,925
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwat
Message 55834 - Posted: 27 Nov 2020 | 8:21:44 UTC

since a few days ago, on one of my machines, the BOINC event log shows the following notice whenever it tries to fetch work:

27.11.2020 09:04:14 | GPUGRID | No tasks sent
27.11.2020 09:04:14 | GPUGRID | Tasks won't finish in time: BOINC runs 99.8% of the time; computation is enabled 100.0% of that

I never had that before; what does this mean? "Tasks won't finish in time" is impossible, since most of the tasks finish whithin one hour (being crunched with at GTX 980Ti)

Profile ServicEnginIC
Avatar
Send message
Joined: 24 Sep 10
Posts: 566
Credit: 5,944,827,024
RAC: 10,700,315
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 55835 - Posted: 27 Nov 2020 | 12:11:39 UTC - in response to Message 55834.

Please, try taking a look to this thread: Only getting 1 GPU work at a time even though set for 10 days of work.
There it was discussed a similar strange notification.

Erich56
Send message
Joined: 1 Jan 15
Posts: 1090
Credit: 6,603,906,926
RAC: 18,783,925
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwat
Message 55836 - Posted: 27 Nov 2020 | 14:49:04 UTC - in response to Message 55835.

Please, try taking a look to this thread: Only getting 1 GPU work at a time even though set for 10 days of work.
There it was discussed a similar strange notification.

thanks for the hint - problem solved :-)

Because of a problem with LHC which I run on that machine, too, a few days ago I had set the workbuffer to 6 days.
In the thread you referred to, it was advised to set this value to less than 5 days, which I did now. And since then, the GPUGRID tasks are being downloaded the way they did before :-)

Post to thread

Message boards : Number crunching : strange notification in event log

//