|
21)
Message boards :
Number crunching :
Scheduler ignoring LHC
(Message 11201)
Posted 5 Nov 2005 by Aurora Borealis Post: Additinal note Predictor and LHC have shorter reporting time. The net effect is that these project tend to force boinc into panic mode and crunching those projects first. This creates a debt that has to be repaid to the other projects and no new WU will be DL until this debt is taken care of. The other projects than get an equal amount of time. It may not be obvious in the short term, and you probably wont see each take there turn in an orderly manner, but over a period of a week or two, it balances out. |
|
22)
Message boards :
Number crunching :
Scheduler ignoring LHC
(Message 11200)
Posted 5 Nov 2005 by Aurora Borealis Post: I am a member of five BOINC projects, all having equal weighting. My computer is always on this time of year and I have noticed that LHC is never scheduled for execution unless I intervene. Stop playing around with it. Every project get its fair share eventually. The more you mess around with it the more the scheduler gets confused and need to rebalance. Boinc works properly on the long run. All your doing is creating debt to the other projects which has to be paid back before LHC will be given priority again. |
|
23)
Message boards :
Number crunching :
I've just upgraded to 5.2.1
(Message 10735)
Posted 14 Oct 2005 by Aurora Borealis Post: <blockquote><blockquote> But be aware that you will not get work from LHC. Until it updates its servers, you will get an error message from LHC that you need V4 to get new work. </blockquote> V4 of what? </blockquote> LHC requires Boinc V4.x and will not supply new work to Boinc V5.x.x until it updates its servers. |
|
24)
Message boards :
Number crunching :
I've just upgraded to 5.2.1
(Message 10733)
Posted 14 Oct 2005 by Aurora Borealis Post: <blockquote>Thank you And I don't need to update the LHC software, correct? That will be done automatically, correct? I only have to update the Boinc software myself, correct?</blockquote> Correct. But be aware that you will not get work from LHC. Until it updates its servers, you will get an error message from LHC that you need V4 to get new work. |
|
25)
Message boards :
Number crunching :
I've just upgraded to 5.2.1
(Message 10731)
Posted 14 Oct 2005 by Aurora Borealis Post: <blockquote>I'm lost with regards to this topic, again. Boinc used to be the only one I could choose the version of, the others, lhc / seti / ..., did it on their own. I have Boinc 4.45, the only version I see as recommended. All project site message boards, lhc / seti / ..., have this topic: version choosing. what's the poop?</blockquote> V5.2.x is probably going to be the next release. It's still under development. The lastest test versions can be found at http://boinc.berkeley.edu/dl/ or http://boinc.berkeley.edu/download.php?dev=1 LHC has not yet updated it's servers to work with V5, but most of the other projects have. |
|
26)
Message boards :
Number crunching :
Resigning due to short deadlines
(Message 9831)
Posted 1 Sep 2005 by Aurora Borealis Post: I generally do not care to get involved in long BB discussions, especially when I must be on the negative side, but I feel a need to clarify my point to the pompom people. What LHC has done with its short deadline WU is jump the queue. This is annoying at best, and absolutely rude in any civilized society. My nice 3 day queue (an acceptable balance in my opinion) which had finally stablelized (with Einstein now using an acceptable deadline) after months of patience, has now again been totally disrupted. LHC's greed has caused other project WU to fall behind and are also now EDF mode. This is not being a good citizen of the Boinc community and will not serve them well in the long run. They are now minus 1 cruncher. This will be my last post on the subject. |
|
27)
Message boards :
Number crunching :
Resigning due to short deadlines
(Message 9821)
Posted 1 Sep 2005 by Aurora Borealis Post: <blockquote><blockquote>I too will be withdrawing my services from LHC. I consider these short deadline WU an attempt to hijack my computer by forcing it into emergency crunch mode, superceding the other projects I crunch for. To me, this action by LHC is on par with adware or a virus. This Project is now in 'No new work' mode and will be suspended as soon as the last WU is returned. I have not yet decided how long I will withdraw my computer, but I am considering a date of January 1st 2006.</blockquote> Nobody has forced you to crunch for LHC, that's your own choiche. The fact that you compare a virus with something that you chose for yourself is quite ridiculous.</blockquote> You are correct I don't 'have' to crunch for LHC, and I won't be for a while. However, having offered my system to help this project doesn't give LHC management the right to abuse my generosity. I believe my action is the best way to reinforce my point. I can only hope that others will join me in my boycott so that the point is made and other projects are not tempted to do the same in the future. |
|
28)
Message boards :
Number crunching :
Resigning due to short deadlines
(Message 9815)
Posted 1 Sep 2005 by Aurora Borealis Post: I too will be withdrawing my services from LHC. I consider these short deadline WU an attempt to hijack my computer by forcing it into emergency crunch mode, superceding the other projects I crunch for. To me, this action by LHC is on par with adware or a virus. This Project is now in 'No new work' mode and will be suspended as soon as the last WU is returned. I have not yet decided how long I will withdraw my computer, but I am considering considering a date of January 1st 2006. |
|
29)
Message boards :
Number crunching :
A new unit
(Message 7793)
Posted 21 May 2005 by Aurora Borealis Post: EDITED I got one. v64lhc.D1-D2-MQonly-inj-no-skew-50s14_16548.4616_1_sixvf_2264 reissued at 8:41:40 UTC I guess I get to lick the bottom of the bowl. |
|
30)
Message boards :
Number crunching :
constant HD activity?
(Message 7387)
Posted 2 May 2005 by Aurora Borealis Post: > Try to let the client run from a MP3-Player, used as a USB-Drive! > > greetz littleBouncer > A warning. I believe, I read somewhere, that USB-Drive, and I presume any MP3-Players also, have a finite number of erase/write cycles. Continuous usage in this way could have a negative effect on its life expectancy. Can anyone confirm or refute this. |
|
31)
Message boards :
Number crunching :
v64lhc.D1-D2-MQonly-inj-no-skew-1s6_8588.2693_1_sixvf_51.zip...???
(Message 7126)
Posted 21 Apr 2005 by Aurora Borealis Post: > > why is it that you guys got work and I didn't????? > > > ok... i hammered the client .... got some.... > It was my turn ---- The last two posting I missed because I'd temporarily paused LHC. ;) |
|
32)
Message boards :
Number crunching :
v64lhc.D1-D2-MQonly-inj-no-skew-1s6_8588.2693_1_sixvf_51.zip...???
(Message 7124)
Posted 21 Apr 2005 by Aurora Borealis Post: I just got a dozen WU a few min ago. They appear to be processing very fast. 9.46 min for the first one. Pausing my other projects to run these WU through. |
|
33)
Message boards :
Number crunching :
Sixtrack 4.67 available
(Message 6992)
Posted 13 Apr 2005 by Aurora Borealis Post: > Let's just clarify this point again: Sixtrack DOES do checkpointing ("periodic > saves") and always has done, BUT there was a bug in version 4.64 which made > this unreliable, leading to the bad effects you are describing. > > Later Sixtrack versions (4.65, 4.66, 4.67 ... ) have corrected this > checkpointing bug. > > Users should stop using 4.64 as soon as possible. (You may have to reset your > BOINC client to trigger the update of your Sixtrack version). > > Ben Segal / LHC@home > No need to reset the project. Install Boinc V4.2x and you can kill individual work unit. |
|
34)
Message boards :
Number crunching :
New WU -- no check point.
(Message 6942)
Posted 10 Apr 2005 by Aurora Borealis Post: > I just discovered this: If you let units stay in memory when suspended, they > won't restart after having been suspended. Strangely enough, they also > continue after the machine has been restarted. > The setting is found under "Your Account" -> "General Preferences" -> > "Leave applications in memory while preempted?". > > Hope this helps you, it certainly helped me. > I forgot to mention this.... because it causes other problems with Windows 98. You end up with several projects apparently running at the same time, and getting very long crunch time to nowhere. I think youre OK with other OS. |
|
35)
Message boards :
Number crunching :
New WU -- no check point.
(Message 6931)
Posted 10 Apr 2005 by Aurora Borealis Post: > I have processed a few of the new work units and they vary in time from 2 to > 35 minutes. > Different WU have various processing time. The S## is your clue. The smaller number seem to take longer. e.g. v64boince6ib1b-37s14 was only 17 min v64boince6ib1b-38s12 was 1 hr currently processing v64boince6ib1b-41s8 already over 3hr Boinc V4.27 alpha |
|
36)
Message boards :
Number crunching :
New WU -- no check point.
(Message 6925)
Posted 9 Apr 2005 by Aurora Borealis Post: > > I got a couple of v64boince WU a few hours ago. > > I checked my message log and have been working on > > v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64 > > It has been paused twice and apparently it has a similar problem to the > old > > LHC WU. It reset to 0% and 0 CPU time when it is restarted. > > > i have the same problem on at least 4 computers. > all intel/winxp/sixtrack4.64 > after every switch between projects the lhc@home wu's restart at 0%. > this way i never get any work done and lhc@home is wasting my donated time. > > resetting these computers makes no difference. > i am not going to stop the other projects i am donating too, to resolve this > problem. > > can i just delete the LHC wu's and hope to get wu's that do work? If you use Boinc V4.2x you can abort individual WU by highlighting them in the Work tab and selecting Abort result in the tasks window. Other than that you could detach from the project, that would kill all the WU. I am not sure what file you need to delete to make WU error out. |
|
37)
Message boards :
Number crunching :
New WU -- no check point.
(Message 6918)
Posted 9 Apr 2005 by Aurora Borealis Post: After several hours of processing, v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64 I had to reboot my computer, and reluctantly decided to abort it. The second WU v64boince6ib1-25s14_16615_1_sixvf_1069_0 using sixtrack version 4.64 completed successfully in only a few minutes. I am now processing v64boince6ib1b-37s14_16630_1_sixvf_28681_1 using sixtrack version 4.66 it seems to pauses and restarts properly. edit:: The above just completed. I had just checked it and it was at 15% a few seconds later it was finished. Successfully !!! I have my doubts. |
|
38)
Message boards :
Number crunching :
New WU -- no check point.
(Message 6904)
Posted 9 Apr 2005 by Aurora Borealis Post: > From which WU do you talk about? Please copy/paste the WU ID or the Link. > And 4.64 are 'old' WU's; the 'new ones' call: 4.66. > > I didn't see any in your resultstable from today an yesterday (8/9.April)! > (you didn't report it yet) > > greetz littleBouncer > It's hard to report a WU that keeps resetting at O% processed. I now need to suspend all my other projects to allow this one to be completed. I will be doing so now and will post again, in four to six hr, when I have completed a WU. |
|
39)
Message boards :
Number crunching :
New WU -- no check point.
(Message 6891)
Posted 9 Apr 2005 by Aurora Borealis Post: I got a couple of v64boince WU a few hours ago. I checked my message log and have been working on v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64 It has been paused twice and apparently it has a similar problem to the old LHC WU. It reset to 0% and 0 CPU time when it is restarted. |
|
40)
Message boards :
Number crunching :
LHC news---- Is there any?
(Message 6817)
Posted 4 Apr 2005 by Aurora Borealis Post: I admit, it's my fault! Every now and then I get tired of the long message page full of e.g. 4/4/05 9:12:00 AM|LHC@home|Requesting 86400.00 seconds of work 4/4/05 9:12:00 AM|LHC@home|Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi 4/4/05 9:12:12 AM|LHC@home|Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded 4/4/05 9:12:12 AM|LHC@home|Message from server: No work available and I suspend LHC. Inevitably a few dozen WU are released during this time. |
Previous 20 · Next 20
©2024 CERN