Message boards :
Technical News :
Splitsville (Aug 16 2007)
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14679 Credit: 200,643,578 RAC: 874 |
So here's the deal. Getting multibeam data out to the public is having its ups and downs. Well, they're holding 8 'tapes' on the server status page - I guess as a sort of 'reserve tank' in case there are more problems with multibeam. Beyond that, I wouldn't know. |
KWSN - MajorKong Send message Joined: 5 Jan 00 Posts: 2892 Credit: 1,499,890 RAC: 0 |
So here's the deal. Getting multibeam data out to the public is having its ups and downs. Looks like they have started splitting it. Splitter status Tape name Host Last block split 16jn00aa penguin 5330 31mr00aa klaatu 16482 30mr00aa kosh 23858 Tapes in splitter queue: 02ap00ab 05mr00aa 28fe00aa 31mr00ab |
edwartr Send message Joined: 2 May 00 Posts: 31 Credit: 79,402,615 RAC: 14 |
I am curious, not hostile. I have been running SETI since 1999. The old Seti used to run great, never any problems and I could store enough units to keep going when the servers did crash. Now I am about ready to take it off my system. It seems SETI is down more than up lately. Is it Seti or Boinc that is the problem? Is it ever going to be fixed? It just seems the "better" the program gets the worse it performs. Well, I have been running SETI since 2000 and while I would agree that there have been more than a few issues in the past couple of months; I would disagree that they are having any more problems than they had under the classic system. I can remember more than a few times under good old SETI classic where it was offline for more than 2 weeks - and some of those times they actually took it offline for more than a week at a time. While I have the desire to crunch SETI more than anything, you can keep going during "down times" by joining another project and turning the processing time down fairly low. Heck, I even set my Rosetta to "get No new tasks" whenever SETI gets back on track. Personally, I would only like to see a bit more information out of the guys during these problem times; however, I also understand that it takes time for this and they are working on fixing the problems. I gotta fever and the only prescription is more cowbell. |
Kim Vater Send message Joined: 27 May 99 Posts: 227 Credit: 22,743,307 RAC: 0 |
I don't think they were less noticeable. But have in mind that those were the "dial-up modem" days, and I think that all active chrunchers were using thirdparty buffer/cache programs. These progs were very easy to find on the Seti main page at that time. I used "SetiBuffer" and never ran out of work - but sure had problems connecting to Seti once in a while ;-) Kiva Greetings from Norway Crunch3er & AK-V8 Inside |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
I don't think they were less noticeable. You're very right, Kiva. I meant to say less-remembered. 8-) |
Keck_Komputers Send message Joined: 4 Jul 99 Posts: 1575 Credit: 4,152,111 RAC: 1 |
I don't think they were less noticeable. They were less noticable as well. For example if there was a splitter problem just resend the results already split. There were no (or more limited) status pages to tell what the servers were doing. I don't remember there being a weekly maintanince outage with classic either. Less remembered because of programs like SETIqueue; because they worked so well participants forget how difficult it was to get work sometimes. This also points to a problem with SETI classic; there were so many queue programs to choose from because it was such a serious problem getting work reliably. There were also no deadlines so it was possible to queue a much larger number of tasks to survive the longer outages. BOINC WIKI BOINCing since 2002/12/8 |
Heechee Send message Joined: 29 Sep 99 Posts: 5 Credit: 13,765,984 RAC: 32 |
I don't think they were less noticeable. I think part of it was the computers where a lot slower then and the work units used to take a long time to crunch. I had a script that would copy data into backup directories to make sure that if the project was down I would have data to crunch. I only needed to store 5 or 6 extra work units to have enough to last most of the outages that SETI had then. An ant on the move does more than a dozing ox. - Lao Tzu |
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0 |
I am curious, not hostile. I have been running SETI since 1999. The old Seti used to run great, never any problems and I could store enough units to keep going when the servers did crash. Now I am about ready to take it off my system. It seems SETI is down more than up lately. Is it Seti or Boinc that is the problem? Is it ever going to be fixed? It just seems the "better" the program gets the worse it performs. The old standalone SETI app. had issues too. Most of them got solved, more or less, with third-party add-ons. ... and according to Matt and others, while the front end looked pretty wonderful, the back end was a mess. With BOINC, problems are more visible -- and the possibilities (like multi-project crunching) are much broader. It's easier for a project to update the science app. because BOINC will do that (classic wouldn't). With reasonable settings, you can also keep crunching right through most outages. I certainly have. It's your call. |
©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.