So here's the deal. Getting multibeam data out to the public is having its ups and downs.

- Matt

Just a quick question...

Now that multibeam data is out (and seemingly stable...for now), what's the status of the old data? Is there any left to be split?

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.

So here's the deal. Getting multibeam data out to the public is having its ups and downs.

- Matt

Just a quick question...

Now that multibeam data is out (and seemingly stable...for now), what's the status of the old data? Is there any left to be split?

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.

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

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.

There's plenty of crunchers that have been here since the beginning that can tell you about some of the nightmares when SETI Classic had problems. They were just less noticeable then. ;)

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

I don't think they were less noticeable.

You're very right, Kiva. I meant to say less-remembered. 8-)

---

I don't think they were less noticeable.

You're very right, Kiva. I meant to say less-remembered. 8-)

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

I don't think they were less noticeable.

You're very right, Kiva. I meant to say less-remembered. 8-)

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.

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

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.

---