Message boards :
Number crunching :
New WU Length?
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · Next
Author | Message |
---|---|
Send message Joined: 29 Dec 07 Posts: 21 Credit: 7,919,038 RAC: 2,295 |
Adding to what Thunder said.....Nate has already said that Travis will increase the deadlines soon,so these short deadlines won't last long ;) Nathan or Travis, will any results from those early batches be accepted if they arrive a few hours late? [http://milkyway.cs.rpi.edu/milkyway/team_display.php?teamid=15]Click here to join the #1 Aussie Alliance on Milky Way.[/url] |
Send message Joined: 29 Dec 07 Posts: 21 Credit: 7,919,038 RAC: 2,295 |
Nathan or Travis, will any results from those early batches be accepted if they arrive a few hours late? The answer was "yes". In my case, the one that was running late by about two hours earned 260 credits. That was a lot of crunching time I didn't want to lose. [http://milkyway.cs.rpi.edu/milkyway/team_display.php?teamid=15]Click here to join the #1 Aussie Alliance on Milky Way.[/url] |
Send message Joined: 29 Aug 07 Posts: 486 Credit: 576,548,171 RAC: 2,784 |
Nathan or Travis, will any results from those early batches be accepted if they arrive a few hours late? The General BOINC Policy is even if a Wu is late if you can get it returned before anybody else does you will get Credit for it. If Somebody else gets issued the Wu because you haven't returned it on time & they return it before you do then a Project Dev would have to manually go in & award you the Credit. Most Project Dev's won't do that as it goes against reason for having a deadline on a Wu in the first place but I have seen exceptions to the rule too where they did do it because of extenuating circumstances. |
Send message Joined: 4 Dec 07 Posts: 45 Credit: 1,257,904 RAC: 0 |
Here's what I've been getting Athlon 64 5600 dual core Short WU ~2.5 hours and Long WU ~5.0 hrs (used to be 5.0 min) Athlon XP 3000, 2800, and 2600 single core Short ~ 3.5 hrs and Long ~7.0 hrs (used to be 7.0 min) Still get a spread of the old 5 or 7 min WU's too. My Athlon 2600 seems to process faster then the 2800 and the 3000. ???? I don't know. |
Send message Joined: 21 Jun 08 Posts: 4 Credit: 2,710 RAC: 0 |
I just have a quick question. I was wondering if the WU length had been increased. I usually complete a WU in about 6.5 minutes but I've gotten a new WU that so far has taken 47 minutes to get to 10.7% completed and is reporting 47 minutes to complete. I thought maybe there might have been a problem with the WU so I suspended the WU and started a new one and it seems like this one is going to be a long completion time as well. I've tried to restart my BOINC Manager to see if there was something going on there but I still had the same long time to complete. Thank you in advance for your help. As posted elsewhere, mine went from 6min to 6.30 Hours... 18 due in 24. Throwing two more squirrels in the comp and hanging bigger treats in front of the wheel. Was going to say nuts, but you know... Heidi-Ann |
Send message Joined: 20 Jan 08 Posts: 2 Credit: 3,677,758 RAC: 0 |
HI! i have got 5 of this monster WU's and cant finish even one within the deadline would be great if this would change next time!! One more question does your app support checkpoints? cu Velo edit: approx. 46% at 3h30m @ Opteron 170 |
Send message Joined: 29 Aug 07 Posts: 486 Credit: 576,548,171 RAC: 2,784 |
HI! LOL ... You want some Monster Wu's you should try Orbit's 200 Hour Plus Monsters, these are just Babys compared to them ... :) One more question does your app support checkpoints? Yes, from what I've seen when I shut dowm BOINC & re-start it again the Wu's start back up again where they left off. The only thing I've seen to the contrary is if the Computer gets kicked off unexpectedly like when it might lose power for a second during a thunder storm the Wu's will error out most of the time ... :) |
Send message Joined: 9 Jul 08 Posts: 85 Credit: 44,842,651 RAC: 0 |
LOL ... You want some Monster Wu's you should try Orbit's 200 Hour Plus Monsters, these are just Babys compared to them ... :) No WU from any project seems long once you've finished your first from climateprediction.net. ;) From a rather "slow" machine and a rather long model (so yeah, admittedly a worst case scenario): CPU time 9,295,941.19 Yes folks, you read that right. 9.2 million seconds or 154932.35 minutes or 2582.21 hours or 107.59 days of CPU time for ONE Workunit. :D Give me your worst MilkyWay... I'm ready! |
Send message Joined: 3 Oct 07 Posts: 5 Credit: 329,770 RAC: 0 |
Just to throw in my 2 cents. 6 hours too long. 3 hours okay. 1-2 hours would be better. My quads go into high priority mode after completing a 6-7 hour w/u. Best case scenario, 1-2 hours with the user being able to choose the cache size (not to exceed 20). Either the user cache size or increase the deadline. Ya can't have long w/u's and short deadlines. There are other projects wanting time too. |
Send message Joined: 16 Apr 08 Posts: 13 Credit: 702,017 RAC: 133 |
I noticed how slow the work units have slowed and dramatically. I love being a part of this since I am an Astronomer but this now, due to the added length of time it take to process a work unit takes away from my other research. I will have to suspend until they clear these lengthy work units away. I have 3 other Astronomy related projects that needs to continue . I will check every few days to see if the work units are a half hour to process again then I will continue. Happy crunching folks :) |
Send message Joined: 29 Aug 07 Posts: 486 Credit: 576,548,171 RAC: 2,784 |
LOL ... You want some Monster Wu's you should try Orbit's 200 Hour Plus Monsters, these are just Babys compared to them ... :) Yes, I've done a few of those Monsters too but didn't mention them because I really don't consider them to be Wu's, their more like Time Travel's than Wu's ... ;) |
Send message Joined: 7 Sep 07 Posts: 444 Credit: 5,712,523 RAC: 1 |
I've done a couple of those, too. You know, if they were any longer I don't think they could call it climateprediction.net ;) Sorry for drifting off topic... |
Send message Joined: 8 Apr 08 Posts: 2 Credit: 601,316 RAC: 0 |
Sorry for all the confusion, I did make a post about the increased time for WUs when I did it, but I realize that "at the same time" wasn't enough time for some of you guys to realize what was going on. Thanks to those that pointed the others in the right direction. If you didn't know how to change the deadlines, wouldn't it have made sense to hold off the changes until all the necessary bits were in place? Due to the short deadlines BOINC is treating MW WU's as high priority, other projects are not getting any time anymore so I've had to stop getting any new WU's |
Send message Joined: 8 Oct 07 Posts: 289 Credit: 3,690,838 RAC: 0 |
The only thing I've seen to the contrary is if the Computer gets kicked off unexpectedly like when it might lose power for a second during a thunder storm the Wu's will error out most of the time ... :) I reported this problem to admin some months ago....nobody else said anything so Dave never looked into....I thought because the work was only a few minutes long either it wasn't noticed or didn't care........now that they are longer... Unexpected shutdowns,normal shutdowns,unusual switching of tasks,aborting another projects work,project suspension/resumtion ,etc can all cause computation errors in milkyway.I think they are all process got signal 11 error. |
Send message Joined: 29 Aug 07 Posts: 486 Credit: 576,548,171 RAC: 2,784 |
The only thing I've seen to the contrary is if the Computer gets kicked off unexpectedly like when it might lose power for a second during a thunder storm the Wu's will error out most of the time ... :) Yes, thats what I get when either Re-Booting or the Computer kicks out, signal 11 error. I haven't noticed it yet if I shut down BOINC First & then Re-Boot but a Re-Boot with BOINC still running will get you that signal 11 error some times. |
Send message Joined: 1 Sep 07 Posts: 18 Credit: 1,658,251 RAC: 0 |
OK I finished my first WU with PII 266Mhz. It took 68+ CPU Hours. And look Here?: 44228711 44988608 16 Jul 2008 19:23:43 UTC 21 Jul 2008 19:54:27 UTC Over Redundant result Cancelled by server 0.00 --- --- 44228710 44988607 16 Jul 2008 19:23:43 UTC 21 Jul 2008 19:54:27 UTC Over Redundant result Cancelled by server 0.00 --- --- |
Send message Joined: 9 Jul 08 Posts: 85 Credit: 44,842,651 RAC: 0 |
Ouch... that might me a machine that just isn't cut out for MW if they increase the WU's as predicted. I don't think a P2/266 could finish any task on any project I'm on within deadline (or at least it would likely take many, many days for even the shortest). Um... are you sure it's even worth the electricity use to run that one anymore? Not that I'd stop you... I've found that some CPUs that are really bad for other projects are actually pretty good for MW, which seems to be very biased towards fast CPU cycle times rather than the changes in more 'modern' architechtures like more pre-fetching, etc. I have a few older P4's that blow the doors off slower (in Mhz only) Core2s and Xeons in MW only. Those slower Core2s and Xeons will however perform much faster with Einstein or SETI, for instance. On a (loosely) related topic, I found it odd that none of my old boxes, even a P3/933 and a Celeron 1200Mhz never had the issue with maximum CPU time exceeded. It would appear that MW left the estimated and max FPOP as the BOINC defaults, which are really quite long. As least I looked in the BOINC documentation and the defaults were the same as what was indicated on the tasks I was working. |
Send message Joined: 1 Sep 07 Posts: 18 Credit: 1,658,251 RAC: 0 |
I'm not sure which projects it was (I thought it was this one but maybe not I'd have to check posts) in early stages the WUs were aborted with because maximum CPU time exceeded. Anyway, I thought it was the projects that was aborting because I don't see a setting In BOINC Manager or BAM to set a CPU Max Time and they weren't running too long before being aborted. Actually, My PIIs don't do too bad. They are definately better than the Cyrus 100 & AMD 100 I retired. Never tried an AMD 25 though :D. I do have more MW WUs left in the PII that aren't going to make it by deadline because when I got them Time to finish was like 20+ minutes but now it's 68+ hours. Hehe. My Pen D 3.0Ghz had a hard time meeting the deadlines but they did. It went from 6 to 9 mins to 9+ hours on them. Hopefully, they are ready to crunch with ease again. |
Send message Joined: 27 Aug 07 Posts: 85 Credit: 405,705 RAC: 0 |
I'm not sure which projects it was (I thought it was this one but maybe not I'd have to check posts) in early stages the WUs were aborted with because maximum CPU time exceeded. Anyway, I thought it was the projects that was aborting because I don't see a setting In BOINC Manager or BAM to set a CPU Max Time and they weren't running too long before being aborted. The max run time is set by the project administrators. I believe that Orbit recently had this problem. BOINC WIKI |
Send message Joined: 24 Jan 08 Posts: 6 Credit: 14,836 RAC: 0 |
|
©2024 Astroinformatics Group