Message boards : Number crunching : No work sent
Message board moderation

To post messages, you must log in.

AuthorMessage
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9290 - Posted: 9 Aug 2005, 19:10:33 UTC

Only 2 Wu´s are in Cache and no new Wu´s are downloaded. (Boinc Manager 4.72)

See: http://lhcathome.cern.ch/results.php?hostid=22496

09.08.2005 20:56:50|LHC@home|Requesting 200089 seconds of work, returning 0 results
09.08.2005 20:56:51|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 20:56:51|LHC@home|Message from server: No work sent
09.08.2005 20:56:51|LHC@home|Message from server: (won't finish in time) Computer on 8.0% of time, BOINC on 99.9% of that, this project gets 100.0% of that

Any Idees

greetings Renato

ID: 9290 · Report as offensive     Reply Quote
Profile Paul D. Buck

Send message
Joined: 2 Sep 04
Posts: 545
Credit: 148,912
RAC: 0
Message 9292 - Posted: 9 Aug 2005, 19:14:51 UTC

Your computer is hardly ever on. So, you need to leave it on more. With it on only 8% of the time ... well, the work won't get done in time.
ID: 9292 · Report as offensive     Reply Quote
Honza

Send message
Joined: 2 Sep 04
Posts: 7
Credit: 30,712
RAC: 0
Message 9293 - Posted: 9 Aug 2005, 19:17:53 UTC

I suggest editing client_state.xml under section of LHC and clear long term debt to zero

http://lhcathome.cern.ch/
LHC@home
...
0

Set time statistics to 1.000.


0.955890
0.936777
0.999040

This will says BOINC that your computer is 100% of time and prevent from this message. Note that this may actually lead to what BOINC says - you might not be able to finish in time when your computer is running BOINC only couple of hours a day.
ID: 9293 · Report as offensive     Reply Quote
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9295 - Posted: 9 Aug 2005, 19:54:22 UTC

I have downgraded to Boinc 4.45 and receive to following Messages:

09.08.2005 21:28:02||request_reschedule_cpus: project op
09.08.2005 21:28:03|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 21:28:03|LHC@home|Requesting 307506 seconds of work, returning 0 results
09.08.2005 21:28:04|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 21:28:04|LHC@home|Message from server: No work sent
09.08.2005 21:28:04|LHC@home|Message from server: (won't finish in time) Computer on 25.9% of time, BOINC on 37.5% of that, this project gets 100.0% of that
09.08.2005 21:28:04|LHC@home|No work from project
09.08.2005 21:28:06|LHC@home|Deferring communication with project for 1 days, 1 hours, 3 minutes, and 28 seconds

All Wu´s uploaded remains "Ready to Report" and no new Wu´s are downloaded.
After the last Wu finished, Wu´s must be "Downloaded" with Update Project.

The editing "client_state.xml" I do not understand
Renato

ID: 9295 · Report as offensive     Reply Quote
Profile littleBouncer
Avatar

Send message
Joined: 23 Oct 04
Posts: 358
Credit: 1,439,205
RAC: 0
Message 9296 - Posted: 9 Aug 2005, 19:57:03 UTC - in response to Message 9293.  

<blockquote>I suggest editing client_state.xml under section of LHC and clear long term debt to zero

http://lhcathome.cern.ch/
LHC@home
...
0

Set time statistics to 1.000.


0.955890
0.936777
0.999040

This will says BOINC that your computer is 100% of time and prevent from this message. Note that this may actually lead to what BOINC says - you might not be able to finish in time when your computer is running BOINC only couple of hours a day.</blockquote>

Thx Honza for this help!
I had the same after I restarted the client (I crunched two weeks with another client) he was at 51% and even it is attached 100% it increases by about 1% per day, what is boring to wait just it reaches at new 'normal' (99-100) %...
This way it is faster corrected.

greetz littleBouncer
ID: 9296 · Report as offensive     Reply Quote
Profile Ageless
Avatar

Send message
Joined: 18 Sep 04
Posts: 143
Credit: 27,645
RAC: 0
Message 9298 - Posted: 9 Aug 2005, 20:05:35 UTC - in response to Message 9297.  
Last modified: 9 Aug 2005, 20:06:16 UTC

<blockquote>All Wu´s uploaded remains "Ready to Report" and no new Wu´s are downloaded.</blockquote>
Please go to your Projects tab in Boincmanager. Select LHC@Home by clicking on it once with the left mouse button. Press the Update button on the left. Wait at least 11 minutes. Press Update again. Trying to update inbetween won't work, you'll get an error message saying that last RPC to the scheduler was less than 10 minutes ago (hence why I say wait at least 11 minutes).

What is the message in the Messages tab now?
Jord

BOINC FAQ Service
ID: 9298 · Report as offensive     Reply Quote
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9300 - Posted: 9 Aug 2005, 20:26:58 UTC

On Computer Lap2 (Boinc 4.72):

09.08.2005 21:58:52|LHC@home|Deferring communication with project for 58 seconds
09.08.2005 21:59:20||request_reschedule_cpus: project op
09.08.2005 21:59:21|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 21:59:21|LHC@home|Reason: Requested by user
09.08.2005 21:59:21|LHC@home|Requesting 11933 seconds of work, returning 0 results
09.08.2005 21:59:22|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 21:59:22|LHC@home|Message from server: No work sent
09.08.2005 21:59:22|LHC@home|Message from server: (won't finish in time) Computer on 8.2% of time, BOINC on 99.9% of that, this project gets 100.0% of that
09.08.2005 22:13:28||request_reschedule_cpus: project op
09.08.2005 22:13:28|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 22:13:28|LHC@home|Reason: Requested by user
09.08.2005 22:13:28|LHC@home|Requesting 35369 seconds of work, returning 0 results
09.08.2005 22:13:29|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 22:13:29|LHC@home|Message from server: No work sent
09.08.2005 22:13:29|LHC@home|Message from server: (won't finish in time) Computer on 8.2% of time, BOINC on 99.9% of that, this project gets 100.0% of that
---------------------------------------------------------------------------
on Computer P3000 (Boinc 4.72 > 4.45):
09.08.2005 22:02:18||request_reschedule_cpus: project op
09.08.2005 22:02:18|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 22:02:18|LHC@home|Requesting 326245 seconds of work, returning 0 results
09.08.2005 22:02:19|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 22:02:19|LHC@home|Message from server: No work sent
09.08.2005 22:02:19|LHC@home|Message from server: (won't finish in time) Computer on 25.9% of time, BOINC on 37.6% of that, this project gets 100.0% of that
09.08.2005 22:02:19|LHC@home|No work from project
09.08.2005 22:02:20|LHC@home|Deferring communication with project for 1 days, 0 hours, 32 minutes, and 14 seconds
09.08.2005 22:14:20||request_reschedule_cpus: project op
09.08.2005 22:14:20||Allowing work fetch again.
09.08.2005 22:14:21|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 22:14:21|LHC@home|Requesting 333036 seconds of work, returning 0 results
09.08.2005 22:14:22|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 22:14:22|LHC@home|Message from server: No work sent
09.08.2005 22:14:22|LHC@home|Message from server: (won't finish in time) Computer on 26.0% of time, BOINC on 37.6% of that, this project gets 100.0% of that
09.08.2005 22:14:22|LHC@home|No work from project
09.08.2005 22:14:23|LHC@home|Deferring communication with project for 1 days, 0 hours, 20 minutes, and 55 seconds

------------------------------------------------------------------------
on Computer Lap3 (Boinc 4.72):
09.08.2005 18:33:53|LHC@home|Deferring communication with project for 1 days, 4 hours, 49 minutes, and 51 seconds
09.08.2005 19:33:53|LHC@home|Deferring communication with project for 1 days, 3 hours, 49 minutes, and 51 seconds
09.08.2005 20:33:54|LHC@home|Deferring communication with project for 1 days, 2 hours, 49 minutes, and 50 seconds
09.08.2005 21:32:37||request_reschedule_cpus: process exited
09.08.2005 21:32:37|LHC@home|Computation for result wjun2C_v6s4hvpac_mqx__8__64.298_59.308__4_6__6__50_1_sixvf_boinc10012_4 finished
09.08.2005 21:32:37|LHC@home|Restarting result wjun2B_v6s4hvpac_mqx__20__64.279_59.289__4_6__6__40_1_sixvf_boinc26439_4 using sixtrack version 4.67
09.08.2005 21:32:38|LHC@home|Started upload of wjun2C_v6s4hvpac_mqx__8__64.298_59.308__4_6__6__50_1_sixvf_boinc10012_4_0
09.08.2005 21:32:40|LHC@home|Finished upload of wjun2C_v6s4hvpac_mqx__8__64.298_59.308__4_6__6__50_1_sixvf_boinc10012_4_0
09.08.2005 21:32:40|LHC@home|Throughput 53155 bytes/sec
09.08.2005 21:33:54|LHC@home|Deferring communication with project for 1 days, 1 hours, 49 minutes, and 49 seconds
09.08.2005 21:53:07||request_reschedule_cpus: process exited
09.08.2005 21:53:07|LHC@home|Computation for result wjun2B_v6s4hvpac_mqx__20__64.279_59.289__4_6__6__40_1_sixvf_boinc26439_4 finished
09.08.2005 21:53:07|LHC@home|Starting result wjun2B_v6s4hvpac_mqx__20__64.286_59.296__10_12__6__65_1_sixvf_boinc26971_1 using sixtrack version 4.67
09.08.2005 21:53:08|LHC@home|Started upload of wjun2B_v6s4hvpac_mqx__20__64.279_59.289__4_6__6__40_1_sixvf_boinc26439_4_0
09.08.2005 21:53:10|LHC@home|Finished upload of wjun2B_v6s4hvpac_mqx__20__64.279_59.289__4_6__6__40_1_sixvf_boinc26439_4_0
09.08.2005 21:53:10|LHC@home|Throughput 50445 bytes/sec
09.08.2005 21:59:50||request_reschedule_cpus: process exited
09.08.2005 21:59:50|LHC@home|Computation for result wjun2B_v6s4hvpac_mqx__20__64.286_59.296__10_12__6__65_1_sixvf_boinc26971_1 finished
09.08.2005 21:59:50||Resuming round-robin CPU scheduling.
09.08.2005 21:59:51|LHC@home|Started upload of wjun2B_v6s4hvpac_mqx__20__64.286_59.296__10_12__6__65_1_sixvf_boinc26971_1_0
09.08.2005 21:59:53|LHC@home|Finished upload of wjun2B_v6s4hvpac_mqx__20__64.286_59.296__10_12__6__65_1_sixvf_boinc26971_1_0
09.08.2005 21:59:53|LHC@home|Throughput 52568 bytes/sec

all Wu´s are finished and no new Wu´s are downloaded.
After Update:

09.08.2005 22:20:46||request_reschedule_cpus: project op
09.08.2005 22:20:46|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 22:20:46|LHC@home|Reason: Requested by user
09.08.2005 22:20:46|LHC@home|Requesting 604800 seconds of work, returning 4 results
09.08.2005 22:20:47|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 22:20:47|LHC@home|General preferences have been updated
09.08.2005 22:20:47||General prefs: from LHC@home (last modified 2005-08-09 20:52:50)
09.08.2005 22:20:47||General prefs: using separate prefs for home
09.08.2005 22:20:48|LHC@home|Started download of wjun2C_v6s4hvpac_mqx__16__64.309_59.319__6_8__6__75_1_sixvf_boinc21688.zip
09.08.2005 22:20:48|LHC@home|Started download of wjun2C_v6s4hvpac_mqx__13__64.292_59.302__4_6__6__15_1_sixvf_boinc16410.zip
09.08.2005 22:20:49|LHC@home|Finished download of wjun2C_v6s4hvpac_mqx__16__64.309_59.319__6_8__6__75_1_sixvf_boinc21688.zip
09.08.2005 22:20:49|LHC@home|Throughput 103899 bytes/sec
09.08.2005 22:20:49|LHC@home|Finished download of wjun2C_v6s4hvpac_mqx__13__64.292_59.302__4_6__6__15_1_sixvf_boinc16410.zip
09.08.2005 22:20:49|LHC@home|Throughput 112078 bytes/sec
09.08.2005 22:20:49|LHC@home|Started download of wjun2C_v6s4hvpac_mqx__5__64.301_59.311__10_12__6__80_1_sixvf_boinc6192.zip
09.08.2005 22:20:49||request_reschedule_cpus: files downloaded
09.08.2005 22:20:49||request_reschedule_cpus: files downloaded
09.08.2005 22:20:49||Using earliest-deadline-first scheduling because computer is overcommitted.
09.08.2005 22:20:49|LHC@home|Starting result wjun2C_v6s4hvpac_mqx__13__64.292_59.302__4_6__6__15_1_sixvf_boinc16410_1 using sixtrack version 4.67
09.08.2005 22:20:50|LHC@home|Finished download of wjun2C_v6s4hvpac_mqx__5__64.301_59.311__10_12__6__80_1_sixvf_boinc6192.zip
09.08.2005 22:20:50|LHC@home|Throughput 121370 bytes/sec
09.08.2005 22:20:50||request_reschedule_cpus: files downloaded
09.08.2005 22:20:50|LHC@home|Pausing result wjun2C_v6s4hvpac_mqx__13__64.292_59.302__4_6__6__15_1_sixvf_boinc16410_1 (removed from memory)
09.08.2005 22:20:50|LHC@home|Starting result wjun2C_v6s4hvpac_mqx__5__64.301_59.311__10_12__6__80_1_sixvf_boinc6192_3 using sixtrack version 4.67

after Update:
09.08.2005 22:22:20||request_reschedule_cpus: project op
09.08.2005 22:22:21|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 22:22:21|LHC@home|Reason: Requested by user
09.08.2005 22:22:21|LHC@home|Requesting 215546 seconds of work, returning 0 results
09.08.2005 22:22:22|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 22:22:23|LHC@home|Started download of wjun2C_v6s4hvpac_mqx__11__64.298_59.308__8_10__6__75_1_sixvf_boinc14136.zip
09.08.2005 22:22:24|LHC@home|Finished download of wjun2C_v6s4hvpac_mqx__11__64.298_59.308__8_10__6__75_1_sixvf_boinc14136.zip
09.08.2005 22:22:24|LHC@home|Throughput 133405 bytes/sec
09.08.2005 22:22:24||request_reschedule_cpus: files downloaded

after update:
09.08.2005 22:23:18||request_reschedule_cpus: project op
09.08.2005 22:23:18|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
09.08.2005 22:23:18|LHC@home|Reason: Requested by user
09.08.2005 22:23:18|LHC@home|Requesting 85964 seconds of work, returning 0 results
09.08.2005 22:23:19|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
09.08.2005 22:23:19|LHC@home|Message from server: No work sent
09.08.2005 22:23:19|LHC@home|Message from server: (won't finish in time) Computer on 14.7% of time, BOINC on 93.3% of that, this project gets 100.0% of that





ID: 9300 · Report as offensive     Reply Quote
Profile Ageless
Avatar

Send message
Joined: 18 Sep 04
Posts: 143
Credit: 27,645
RAC: 0
Message 9301 - Posted: 9 Aug 2005, 20:41:35 UTC - in response to Message 9300.  
Last modified: 9 Aug 2005, 20:42:18 UTC

Okay, so 2 of your computers have work again. The third doesn't (yet).

What you may want to do is edit your Connect To amount of days and half it. You do this in your preferences. Change the Connect To amount there to 3 (days), save the changes, then Update LHC again in Boinc Manager (Just press the Update button).

At present your first computer is asking 7 days of work, while the deadline for work units is varying. There are now 7 day deadline units for LHC, so if you ask 7 days, but your computer isn't on for 24/7, or not running Boinc 24/7 (24 hours per 7 days), you won't get new work. (Is what Paul was hinting at)

By setting your connect to x days to a lower amount, you will get work. Maybe not as much as you are used to, but if you run the computer every day for 8 hours, while it has the option to get online, it shouldn't matter. It will then happily upload & download.

Next time you're stuck on not getting work, make sure you report the work units. That will usually help on clearing the work queue, so neither LHC nor Boinc think there's still work in it.
Jord

BOINC FAQ Service
ID: 9301 · Report as offensive     Reply Quote
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9302 - Posted: 9 Aug 2005, 21:15:48 UTC

all my 7 Computers are 24/7
and every one as others Problems with downloading Wu´s

my next action is on all PC´s,
deinstall Boinc, delete all Boinc Files and reinstall Boinc

thanks for help
Regard´s Renato
ID: 9302 · Report as offensive     Reply Quote
Profile littleBouncer
Avatar

Send message
Joined: 23 Oct 04
Posts: 358
Credit: 1,439,205
RAC: 0
Message 9304 - Posted: 9 Aug 2005, 22:23:42 UTC - in response to Message 9302.  
Last modified: 9 Aug 2005, 22:44:01 UTC

<blockquote>all my 7 Computers are 24/7
and every one as others Problems with downloading Wu´s

my next action is on all PC´s,
deinstall Boinc, delete all Boinc Files and reinstall Boinc


thanks for help
Regard´s Renato</blockquote>

That is the 'hardest way', but it will help....

BTW: If you run LHC solo: Stop BOINC, delete the files 'client_state.xml' and 'client_state_prev.xml' in the BOINC-folder , then start BOINC at new. Ignore the errormessage in the message tab and when necessary: update. It will produce new 'xml' files how after a new installation. This works with CC 4.19, with CC 4.45 I never tried (because this client is attached on several projects).

greetz littleBouncer
ID: 9304 · Report as offensive     Reply Quote
Jayargh

Send message
Joined: 24 Oct 04
Posts: 79
Credit: 257,762
RAC: 0
Message 9310 - Posted: 10 Aug 2005, 1:46:30 UTC
Last modified: 10 Aug 2005, 1:47:41 UTC

Geez ya'll ...these convoluted solutions... just suspend any other projects... it downloads....unsuspend other projects... and ltd gets corrected 4.25...4.45...or...4.72.... why make it harder than it needs to be?
ID: 9310 · Report as offensive     Reply Quote
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9314 - Posted: 10 Aug 2005, 7:52:32 UTC - in response to Message 9304.  

<blockquote>BTW: If you run LHC solo: Stop BOINC, delete the files 'client_state.xml' and 'client_state_prev.xml' in the BOINC-folder , then start BOINC at new. Ignore the errormessage in the message tab and when necessary: update. It will produce new 'xml' files how after a new installation. This works with CC 4.19, with CC 4.45 I never tried (because this client is attached on several projects).

greetz littleBouncer</blockquote>

Thanks littleBouncer, it´s work with 4.45 and 4.72
ID: 9314 · Report as offensive     Reply Quote
Profile Ageless
Avatar

Send message
Joined: 18 Sep 04
Posts: 143
Credit: 27,645
RAC: 0
Message 9326 - Posted: 10 Aug 2005, 14:55:15 UTC - in response to Message 9310.  

<blockquote>Geez ya'll ...these convoluted solutions... just suspend any other projects... it downloads....unsuspend other projects... and ltd gets corrected 4.25...4.45...or...4.72.... why make it harder than it needs to be?</blockquote>
That's fine... if he is running other projects. Which I never asked, plus don't read from his messages. So how would you do it if you're only running LHC? Suspend LHC? ;)
Jord

BOINC FAQ Service
ID: 9326 · Report as offensive     Reply Quote
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9392 - Posted: 14 Aug 2005, 19:43:46 UTC

after deleting all 'client_state.xml' and 'client_state_prev.xml' work´s will be downloaded.

The finished WU´s are uploaded and remain not counted until the Update Function is activated.

Any Idees to change this Error


ID: 9392 · Report as offensive     Reply Quote
Profile Jim Baize
Avatar

Send message
Joined: 17 Sep 04
Posts: 103
Credit: 38,543
RAC: 0
Message 9395 - Posted: 15 Aug 2005, 6:41:24 UTC - in response to Message 9392.  

Actually, what you are experiencing is not an error, instead it is the proper function of BOINC.

uploading and reporting of WU's is a two step process. The first step is to send in the data. The second step is to report the data to the database.

The first step is done automagically as soon as the computations have completed. The second step will occur the next time the client contacts the server. It's all automagic.

More detailed explainations can be found in the WIKI.

<blockquote>The finished WU´s are uploaded and remain not counted until the Update Function is activated.

Any Idees to change this Error

</blockquote>
ID: 9395 · Report as offensive     Reply Quote
Renato

Send message
Joined: 30 Sep 04
Posts: 10
Credit: 453,414
RAC: 0
Message 9410 - Posted: 15 Aug 2005, 20:20:50 UTC

The Problem is: I have reduced "Connect to network about every" from 7 to 0,5 Days and this results: no new Wu´s are requested and the returning of results are not taken.

I have installed BoincView 1.02 and with on Button Click all results are updated. Great Tool. Work also over xxx.dyndns.org and Zywall

ID: 9410 · Report as offensive     Reply Quote
Jayargh

Send message
Joined: 24 Oct 04
Posts: 79
Credit: 257,762
RAC: 0
Message 9416 - Posted: 15 Aug 2005, 23:47:25 UTC - in response to Message 9395.  

<blockquote>Actually, what you are experiencing is not an error, instead it is the proper function of BOINC.

Yes this is somewhat true Jim because in practice Boinc 4.45 will auto report without requesting new work (nice little feature that no other versions have to my knowledge) but 4.72 will not auto report :( as I am now using 4.72 so I don't have to have a 10 day work cue to get 3 days work and can now again rejoin other projects
ID: 9416 · Report as offensive     Reply Quote
Profile Jim Baize
Avatar

Send message
Joined: 17 Sep 04
Posts: 103
Credit: 38,543
RAC: 0
Message 9418 - Posted: 16 Aug 2005, 0:22:51 UTC - in response to Message 9416.  

I am using 4.72 and I have never had an instance where it did not autoreport. Most of my machines run without intervention or without supervision. I check on them about once a day to make sure they are running, other than that, I don't mess with them. All of my WU's get uploaded and reported just fine.

<blockquote><blockquote>Actually, what you are experiencing is not an error, instead it is the proper function of BOINC.

Yes this is somewhat true Jim because in practice Boinc 4.45 will auto report without requesting new work (nice little feature that no other versions have to my knowledge) but 4.72 will not auto report :( as I am now using 4.72 so I don't have to have a 10 day work cue to get 3 days work and can now again rejoin other projects</blockquote>
ID: 9418 · Report as offensive     Reply Quote
Jayargh

Send message
Joined: 24 Oct 04
Posts: 79
Credit: 257,762
RAC: 0
Message 9419 - Posted: 16 Aug 2005, 0:40:45 UTC - in response to Message 9418.  
Last modified: 16 Aug 2005, 0:53:00 UTC

<blockquote>
Jim key word in my statement is without requesting new work.... if you are on automatic you may never had realized 4.45 will send in less than 1 minute to report 95% of time w/o new work request which on 4.72 may take hours on a higher work cue (more than 1 day) [EDIT] Trying to be clearer in my answer to you Jim and all...I had been running only LHC with a 10 day connect to network giving me 3 days of work with Boinc 4.19,4.25,4,45 and now 4.72 until LHC changed deadline at same time 4.72 was working better with time to completions.... I brought time to connect down to now 4 days and may take up to 8-12 hours to report (reporting only when asking for new work) due to the ever changing time to connect every time I finish a workunit. Boinc 4.45 would again report and NOT ask for new work in less than a minute[EDIT]
ID: 9419 · Report as offensive     Reply Quote

Message boards : Number crunching : No work sent


©2021 CERN