Have faith, they will get it right. If you dont think that...WHY are you here?

One of the major reasons as to why I'm here is support for Distributed Computing (DC).

Computers and computing is one of the greatest achievments of the 20th Century.
Seti@Home has led to the implementation of BOINC, one of the leading DC platforms.
Far too many of Humanity's resources are being wasted or lost.
It would be a terrible shame to not use the available resource of idle cpu cycles for the benefit of all humanity.

We are still in the early days of DC, and like all scientific projects, it will continue to be developed and improved.

I want to do my (little) bit to help.

:)

---

Join TeamACC

Sometimes I think we are alone in the universe, and sometimes I think we are not. In either case the idea is quite staggering.

Not real clear that shutting down classic will actually help.

That is, while that will certainly free up additional hardware for SETI BOINC, it may also redirect the still quite large population of SETI classic workstations to SETI BOINC.

The thing is, with the validation process, running BOINC in more resource intensive -- both in terms of CPU utilization and system I/O. Lot's of cross checking, lots of units going inbound and outbound and (seemingly) more complex code.

Then again, I don't know that BOINC is the issue -- as there are other BOINC projects (admittedly currently only about 1/4 the host load each as SETI) which are running essentially rock solid and have been for months.

As it is, the SETI folks have been struggling with a batch of issues, hardware, software, connectivity and electrical which no doubt have been causing a fair amount of frustration -- not only for the SETI BOINC user population, but also for the the folks at the lab.

The current validator outage seems to be to have at least the *scent* of 'let's try this, it might work' about it rather than a case of an 'ah ha!' solution about it.

Also, a few weeks ago, Berkeley posted a notice about the difficulty in keeping up with requests for work -- if the remaining active SETI classic folks were to switch over, then that issue also would be a problem here.

And of course in addition to these issues which are 'can we keep up with the *current* workload' issues, there are the 'rifle shots' of hardware failures, electrical issues, connectivity issues which in their own way add to the keep up with the workload issues by generating surges.

So, I guess at this point, given the resources and environment that Berkeley is working with, I am NOT sanguine about SETI BOINC being able to keep up with a future increase in workload (heck they have more than enough problems keeping up with the current workload).

FYI The "anticipated" load is about 1 million work units per day, regardless of the number of users. I THINK we are actually approaching this number right now but I can't say for sure. But yes, it is very possible to achieve using current technology although certainly not cheap. Currently there is also the issue of the server closet being full. Seti classic shutting down will help with that :)

---

Have faith, they will get it right. If you dont think that...WHY are you here?

---

FYI The "anticipated" load is about 1 million work units per day, regardless of the number of users. I THINK we are actually approaching this number right now but I can't say for sure. But yes, it is very possible to achieve using current technology although certainly not cheap. Currently there is also the issue of the server closet being full. Seti classic shutting down will help with that :)

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

With the hardware and software available today, is a project the size and scope of the anticipated Boinc/Seti achievable?

When you say "available today" do you mean the hardware they already own, or hardware that is available to be bought...

If you mean "what they already own" I dont think it's going to be up to the job in the future, as it is already not up to it in the present. :'-(

Odd. I'm able perform work on this project perfectly well enough. Evidently you cannot. Who's the one with the brain damage?

You are.. When was the last time the validator granted you credits? Why would a 5 hour outage cause this kind of a scramble by UCB if the current system could handle the "current load", much less the "anticipated load"?

You look interesting in that cheerleader outfit, but I'd sugest that you get a bikini wax if you keep getting your panties in a bunch!

Remember you are are one that missed the "antisipated" part of the question, and now you're are doing your best to obsure that part of the question, as you can't admit you were wrong!

You messed up and either let it drop, or admit it!

---

Odd. I'm able perform work on this project perfectly well enough. Evidently you cannot. Who's the one with the brain damage?

---

Sorry, az... I don't anticipate what I'm already doing. ;)

If you're aware of a distinction between what the BOINC SETI@home project is now and what it is *anticipated* to be, please enlighten us. I think if you ask 10 people what they anticipate from this project and you're bound to get a dozzen different answers. Trying to measure up to such speculation is rather pointless...

Simple... Only about 1/2 of the classic crunchers have moved to seti/boinc. The question WAS about anticipated load!

Darn.. You got the pompom to far in your ear that it damaged some brain cells!

Even if the current HW could handle the current load (without shutting down services for days to recover from a 5 hour outage), seti/boinc is not handling even 1/2 the load of classic. (and it seems that adding servers might help little, if the bottleneck is the interface bwtween the servers! (100mb)

The classic seti HW if all switched to seti/boinc over night, probably couldn't handle the same number of users as classic. The backend (server) system with seti/boinc seem to be much more complex than classic, and will require more CPU/MEMORY/DISK/IO than classic.

---

Sorry, az... I don't anticipate what I'm already doing. ;)

If you're aware of a distinction between what the BOINC SETI@home project is now and what it is *anticipated* to be, please enlighten us. I think if you ask 10 people what they anticipate from this project and you're bound to get a dozen different answers. Trying to measure up to such speculation is rather pointless...

---

Vote using thread (+) or (–) on the thread rating.

Disregarding the current problems and so forth answer this question.

With the hardware and software available today, is a project the size and scope of the anticipated Boinc/Seti achievable?

(+) = yes
(-) = no

Thanks for voting!

For what's available in general today (HW and people), yes (+)
For what's available at UCB today (HW and people), no (-)

There are still a boatload of people running classic that don't read any seti forums that will switch over when the "notification" (email or thru the classic cruncher) goes out, or maybe when they stop getting classic work, and they check the website.

As the URL that many are used to now point's to seti/boinc, it might be a good thing to have some note on the front page to welcome classic users, and let then know why they are now pointed at a new website. (not a news item that can scroll off), but a notice on the site itself) While the "notification" might also include this info, there will be some that don't get the notification, and hit the site when then can no longer upload/download work for classic.

They're still recovering from a 5 hour outage days ago, and have a much longer outage planned starting this weekend. This will be interesting. I myself have seti/boinc turned off right now for all systems.

BTW, Mr. David Knittle - the word " anticipated" was used in the question!

---

:P

- +

---

+ -

---

Psssttt! Don't look now, but a project like this is achievable because we're already doing it!

---

Vote using thread (+) or (–) on the thread rating.

Disregarding the current problems and so forth answer this question.

With the hardware and software available today, is a project the size and scope of the anticipated Boinc/Seti achievable?

(+) = yes
(-) = no

Thanks for voting!

yes they evently need seporate machines for each prosess instead of share like they do now and in the future may need more than one each for upload download validate and delete.

---

Vote using thread (+) or (–) on the thread rating.

Disregarding the current problems and so forth answer this question.

With the hardware and software available today, is a project the size and scope of the anticipated Boinc/Seti achievable?

(+) = yes
(-) = no

Thanks for voting!

---

Boinc....Boinc....Boinc....Boinc....