Message boards :
Number crunching :
Astropulse Grrr...
Message board moderation
Author | Message |
---|---|
Iserlohner Send message Joined: 19 Feb 00 Posts: 5 Credit: 476,328 RAC: 1 |
I've just had to abort 2 Astropulse WU's @ 60% complete as they wouldn't have made the report deadline. I've also just aborted another Astropulse WU that was ready to start as again it wouldn't have made the report deadline. Seens that the long run times and the report deadline aren't correlated to me. So Astropulse has cost me today alone around 24 hrs of crunching on two CPU's :( Credit I might add that I won't now be getting, if I'd let the WU's run, the first would have been around 10 hours overdue, the second around the same, the ready to start would have been 30-40 hours over due. Come on SETI get a grip and give us a fighting chance of completing an Astropulse WU. I don't want to stop crunching SETI as we've been crunching together for almost 9 years now, but Astropulse is killing any loyalty I have with you. PC Spec BTW Core 2 Quad Q6600 8MB cache 2GB Corsair DDR2 XMS2-6400C4 TwinX (SLI) 2 x BFG GeForce 8800 GTS 640MB PCI Express 2 x 320GB Caviar SE16 SATA 300 (RAID 0) So my PC isn't a complete dog, just the timings aren't correlated Cheers Iser |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
I've just had to abort 2 Astropulse WU's @ 60% complete as they wouldn't have made the report deadline. Even if you're not overclocked and don't run the optimized Astropulse-application, your computer should have no problem to finish a Astropulse-wu within the deadline if runs atleast 2 hours/day... So, something doesn't seem to add-up here... Hmm, it's a problem that the "duration correction factor" after running a string of seti-wu's will be too low for Astropulse, so the expected run-time will be shorter than reality. This can lead to, if you're sharing with other projects and SETI@home has a low resource-share, that SETI@home doesn't get enough resources. Another possibility is you're running with a fairly large cache, and gets a string of VHAR-wu's with a short deadline, so they're being crunched 1st., and the Astropulse gets delayed... If low resource-share, increasing resource-share should hopefully fix it, and if large cache-size, reducing the cache-size should hopefully fix it. Another option is to either not run Astropulse and only SETI_Enhanced, or, to only run Astropulse and not run SETI_Enhanced. Which application to run is selectable under SETI@home preferences. You can have upto 4 different "venues", in case of multiple computers. In case of only Astropulse, either set "no new work" and finish your already-cached seti-wu and report it and afterwards reset and enable work again, or detach/re-attach. It's also possible to manually edit client_state.xml, and increase the duration correction factor to 0.5 or something... Oh, and even if you're 10 hours after the deadline, since no-one can manage to crunch an Astropulse-wu so fast, you'll still get your credits for the work. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
gizbar Send message Joined: 7 Jan 01 Posts: 586 Credit: 21,087,774 RAC: 0 |
Hi Iserlohner, Just remember that it has been said that if you do not make the deadline for Astropulse units and Seti sends the Wu's out to a third party, due to the long crunch times of the Wu's, you would still report them and get the credit for them long before anybody else could get them finished. So I'm afraid to say that the only reason that you won't get the credit for them is because you have cancelled them. This has been discussed and detailed on here already (but I can't remember which thread), so if you'd researched the problem a little bit before cancelling them, you'd be sitting pretty on a pile of credit for them. Hope that helps for next time. Regards, Gizbar. A proud GPU User Server Donor! |
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0 |
Compared to yours, my machine is a complete dog. It's an Athlon XP 3000+ and I only crunch 16 hours/day. I do only Astropulse. Work completes with plenty of time to spare. The stock AP application takes 150 hours of CPU (optimized is 60 hours). I'd encourage you to let the next one run, and not worry about deadlines until it actually misses some. |
©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.