SETI doesn't request new work - what's the problem?

Message boards : BOINC client : SETI doesn't request new work - what's the problem?
Message board moderation

To post messages, you must log in.

AuthorMessage
Laurent

Send message
Joined: 17 Dec 07
Posts: 4
United Kingdom
Message 14370 - Posted: 17 Dec 2007, 10:52:05 UTC

BOINC 5.10.28.
SETI Enhanced 5.27.
_________________________________________
I run Climate prediction and SETI.
100% CPU all times, 2Meg cable permanent connection.
Problem:
Regularly SETI does NOT report results for days, even when more than 1 run is finished.
Similarly SETI does NOT request new work even when all work is finished.
When I eventually use UPDATE button, which often requires more than one attempt, all it does is send results; no new work is REQUESTED by SETI at my end.
This is only resolved when I press Reset Project for SETI. It then usually receives two SETI work units.
Can anyone help with this please?
ID: 14370 · Report as offensive
Laurent

Send message
Joined: 17 Dec 07
Posts: 4
United Kingdom
Message 14371 - Posted: 17 Dec 2007, 10:53:43 UTC - in response to Message 14370.  
Last modified: 17 Dec 2007, 10:54:11 UTC

Help?
ID: 14371 · Report as offensive
SekeRob

Send message
Joined: 25 Aug 06
Posts: 1596
Message 14372 - Posted: 17 Dec 2007, 11:12:49 UTC - in response to Message 14371.  

The origin lies in that you run multiple projects. Depending on weight at times, BOINC will pause work fetch to let other projects reduce their LTD/STD credit. If CPDN is heading for the deadline, eventually BOINC will stop all work fetch until CPDN is finished.

Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 14372 · Report as offensive
Laurent

Send message
Joined: 17 Dec 07
Posts: 4
United Kingdom
Message 14373 - Posted: 17 Dec 2007, 11:18:27 UTC

Ok, thanks.
You are refering to "Resource share"?
I did have CPN set to 9 and SETI set to 1.
I have changed both to 100, the default i think.
Have I understood your explanantion?
ID: 14373 · Report as offensive
MikeMarsUK

Send message
Joined: 16 Apr 06
Posts: 386
United Kingdom
Message 14374 - Posted: 17 Dec 2007, 11:24:49 UTC


What is the deadline on your CPDN task?

ID: 14374 · Report as offensive
Laurent

Send message
Joined: 17 Dec 07
Posts: 4
United Kingdom
Message 14375 - Posted: 17 Dec 2007, 11:27:51 UTC

CPDN 21/11/2008
SETI 24/01/2008
SETI 24/01/2008
ID: 14375 · Report as offensive
MikeMarsUK

Send message
Joined: 16 Apr 06
Posts: 386
United Kingdom
Message 14407 - Posted: 18 Dec 2007, 10:15:58 UTC


The November 2008 deadline should be fine as long as you're doing at least one model year per 5 days (there are 72 model years in a HadSM3 model).

Do any tasks say 'high priority'? How much credit do you get per day overall? (If you're getting less than around 40 credit per day that might be what the problem is).


ID: 14407 · Report as offensive
Heflin

Send message
Joined: 26 Jun 07
Posts: 29
Message 14419 - Posted: 18 Dec 2007, 23:04:39 UTC - in response to Message 14370.  

Regularly SETI does NOT report results for days, even when more than 1 run is finished.
Also, there are TWO portions/actions for reporting work.
1) uploading the results of the WU to one server
2) then reporting the WU is complete to another server.

The second step often waits until you have some other reason to contact that server like requesting new work or reporting more than 1 WU complete. It is less_load on the server when clients do multiple reports together, vice multiple clients hammering the server with just 1 WU complete status reports.

As long as your BOINC client is working on something, all the other stuff (upload results, reporting complete, meeting your resource shares) will get done in due time.

I have one client that waits days before reporting a whole bunch of completed tasks. As long as they are reported before the deadline-date, no problem.

ID: 14419 · Report as offensive

Message boards : BOINC client : SETI doesn't request new work - what's the problem?

Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.