Message boards :
Number crunching :
Got *no* new work...
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
W-K 666 Send message Joined: 18 May 99 Posts: 19136 Credit: 40,757,560 RAC: 67 |
By stabilised I mean that - My Q6600 also shows that that the improvements done in AP r103, now mean there is little variation in DCF between MB and AP. It would seem the DCF is fairly stable at about 0.11 +/- 0.01. |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
By stabilised I mean that - My E8500 has been doing VLAR work, so DCF is at 0.16, Because of that Boinc reckons AP work is going to take 12½hrs each, But with r103 AP, it'll take 6½ to 7 hrs, and DCF will dive. Claggy |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
It looks like my main PC got hit with the "no new work" download anyway. From what I saw the scheduler sent the message of no work available. so I hit the NNT button. next thing I know its hitting me with more work. Now I do have a my cache set to 7+ days so I'm not all that disturbed by the amount of work. I know I'll finish it on time. I was just surprised when it did send the tasks 1/24/2009 5:56:37 PM|3x+1@home|Scheduler request succeeded: got 0 new tasks In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 |
My E8500 has been doing VLAR work, so DCF is at 0.16, Because of that Boinc reckons AP work is going to take 12½hrs each, Bear in mind that downward DCF adjustment is gradual. One AP which was estimated at 12.5 hours and actually crunched in 6.5 hours will reduce DCF by less than 5%. It's a low gravity dive. Joe |
Jonathan Send message Joined: 1 Oct 07 Posts: 5 Credit: 1,263,835 RAC: 101 |
So, to those of use with less than 2 phd's, how do I get it to download more work? My first couple of lines btw. 25/01/2009 21:14:51||Starting BOINC client version 6.4.5 for windows_intelx86 25/01/2009 21:14:51||log flags: task, file_xfer, sched_ops 25/01/2009 21:14:51||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3 25/01/2009 21:14:51||Data directory: E:\Utilities\Web\Bionic\xxdata 25/01/2009 21:14:51||Running under account Jonathan 25/01/2009 21:14:51||Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz [x86 Family 6 Model 15 Stepping 2] 25/01/2009 21:14:51||Processor features: fpu tsc pae nx sse sse2 mmx 25/01/2009 21:14:51||OS: Microsoft Windows XP: Home x86 Editon, Service Pack 3, (05.01.2600.00) 25/01/2009 21:14:51||Memory: 1.99 GB physical, 3.84 GB virtual 25/01/2009 21:14:51||Disk: 72.72 GB total, 52.81 GB free 25/01/2009 21:14:51||Local time is UTC +0 hours 25/01/2009 21:14:51||Not using a proxy 25/01/2009 21:14:51||CUDA devices found 25/01/2009 21:14:51||Coprocessor: GeForce 9600 GT (1) 25/01/2009 21:14:51|rosetta@home|URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 983631; location: (none); project prefs: default 25/01/2009 21:14:51|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 1804331; location: (none); project prefs: default 25/01/2009 21:14:51|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4712958; location: home; project prefs: default 25/01/2009 21:14:51||General prefs: from http://bam.boincstats.com/ (last modified 12-Jan-2009 19:54:03) |
Mibe, ZX-81 16kb Send message Joined: 30 Jun 99 Posts: 42 Credit: 2,622,033 RAC: 0 |
Ok, I think i got it. The cache size calculation varies and it only give you a ball-park figure. That was why my client requested 0 seconds of work even though 2 cores sat idle. "OzzFan" wrote:
Yes I tried 10 days, since my 2 day setting ran out of work. But I don't want a 10 day cache, so whenever all my cores get busy I'll change it back to 2 days. I think the problem I had was that it requested 0 seconds, otherwise the connection would have failed, or the server would have answered with "no work available". I could be wrong here since i have no clue how the serverside behave. "Claggy" wrote:
Yes, I found out that it was easier/faster to change the settings in the gui. I'll try the web-conf when my 2 day cache is back. Thank you all for your answers and information. My cache is slowly building up to it's previous size. I can only hope this wont happen again... :-) |
Jonathan Send message Joined: 1 Oct 07 Posts: 5 Credit: 1,263,835 RAC: 101 |
nm, got it, I changed settings from 3 days to 10 and got a little more work. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
Older versions of BOINC have sever restrictions on work fetch if there is work that is in danger of being late. Please note that if the work is not completed before Connect Ever X before the report deadline, there is no way that BOINC can hope to have the report done before the deadline. Therefore if might complete after that, it is considered in danger of being late. This was removed in the most recent couple of versions at the risk of reporting work late. Full caches of both connect every X and extra work is too much, and work will be reported late. BOINC WIKI |
W-K 666 Send message Joined: 18 May 99 Posts: 19136 Credit: 40,757,560 RAC: 67 |
Older versions of BOINC have sever restrictions on work fetch if there is work that is in danger of being late. Please note that if the work is not completed before Connect Ever X before the report deadline, there is no way that BOINC can hope to have the report done before the deadline. Therefore if might complete after that, it is considered in danger of being late. This was removed in the most recent couple of versions at the risk of reporting work late. Full caches of both connect every X and extra work is too much, and work will be reported late. Seems like another one of those cases where the original good design has been corrupted because of pressure from parties that were too lazy to find out how the schedulers works, in regard to their own practices. And not realising the effect on other projects. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
Older versions of BOINC have sever restrictions on work fetch if there is work that is in danger of being late. Please note that if the work is not completed before Connect Ever X before the report deadline, there is no way that BOINC can hope to have the report done before the deadline. Therefore if might complete after that, it is considered in danger of being late. This was removed in the most recent couple of versions at the risk of reporting work late. Full caches of both connect every X and extra work is too much, and work will be reported late. Agreed. |
©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.