Ready to send 425,048

What will happen if they run out?

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1052&amp;prj=1&amp;trans=off">
<img src="http://seti.mundayweb.com/stats.php?userID=749&amp;trans=off">

> What will happen if they run out?

Connecting to the server, you will simply get a Message "No Work from Project".

The Splitters will feed in all they can, so it will initially be a bit of luck to connect when those have just finished preparing another bunch of WorkUnits for Download (with 3 Splitters this happens a few times per hour AFAIK).

---

Quit you're whining and look down........


June 4, 1999

We learned that the SETI@home server has been repeatedly issuing the same 115 work units for the last few days. This was fixed immediately, and we put a notice on the web site. We're back to issuing our existing 31,415 work units. The problem was due to a subtle operating system bug, but we feel bad that we didn't catch it sooner.

June 1, 1999

Sun Microsystems has offered a substantial donation of new hardware: 4 workstations, 4 DLT drives, a large amount of disk storage, and a 450 4-CPU Enterprise Server. The workstations and tape drives are schedule to arrive 6/15, and the 450 is slated for end of June.

May 29, 1999

The receiver front end at Arecibo is not working; engineers are working to fix. Fortunately we still have a large backlog of tapes starting from December 1998.

May 28, 1999

Quantum has donated about 360 GB of disk drives.

May 27, 1999

To address performance problems, we have changed the way our server works. Before, when a user requests a work unit, the SETI@home server queried the database server to find the best work unit to send, and it updated the "# work units sent" field of the user, their country, their team, etc. This was overloading the database. In our new scheme, the SETI@home server avoids using the database as much as possible. It generates "flat files" that record work units sent and results received. An off-line program processes these files and updates the accounting records in our database.

As a result of this "delayed accounting", users won't see credit for their results immediately on the web site or in their screensaver. There will a delay, depending on how far behind the off-line processing gets.

We changed the word "Team" to "Group" on the web site because the SETI Institute has a fundraising program called "Team SETI", and there was concern about confusion.

May 25, 1999

Our fix to the team mechanism has ANOTHER loophole. We changed the mechanism again (this time for sure??). We didn't zero out group membership this time.

May 24, 1999

Our Team mechanism has a problem: it's possible to add any user to your team. Some teams have used this loophole to "hijack" users with lots of CPU time. We fixed this (we thought) and emptied out all teams.

May 23, 1999

We added the "Team" mechanism.

May 22, 1999

Because of the unexpectedly large number of users, our server has become overloaded. Clients are unable to connect and get error messages. We're getting thousands of email messages every day about this.

To reduce the CPU load on WS3 we have temporarily stopped running the Splitter. We have 31,415 work units on disk right now, and we'll issue these until we can start generating new ones.

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

> Ready to send 425,048
> What will happen if they run out?

As FalconFly said: 'No work from project' will be really a possible message.
@Classic they sent out just the same stuf again and again and again, sometimes up to 30 times, just to please the crowd. This will not happen here. If nothing's there for the moment, just crunch one of the other projects. Or save energy. But no useless rounds of redundant crunching.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

Database status
State Approximate #results
Ready to send 425,048
In progress 2,388,428
Waiting for validation 1
Waiting to transition 1

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1052&amp;prj=1&amp;trans=off">
<img src="http://seti.mundayweb.com/stats.php?userID=749&amp;trans=off">

Database status
State Approximate #results
Ready to send 406,041
In progress 1,045,304
Waiting for validation 0
Waiting to transition 1

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1052&amp;prj=1&amp;trans=off">
<img src="http://seti.mundayweb.com/stats.php?userID=749&amp;trans=off">

> Database status
> State Approximate #results
> Ready to send 406,041
> In progress 1,045,304
> Waiting for validation 0
> Waiting to transition 1
>

So what?
I can read this myself on the server status page.

Database status
State Approximate #results
Ready to send 406,041
In progress 1,026,600
Waiting for validation 18
Waiting to transition 1

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1052&amp;prj=1&amp;trans=off">
<img src="http://seti.mundayweb.com/stats.php?userID=749&amp;trans=off">

Database status
State Approximate #results
Ready to send 406,041
In progress 2,157,840
Waiting for validation 18
Waiting to transition 1

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1052&amp;prj=1&amp;trans=off">
<img src="http://seti.mundayweb.com/stats.php?userID=749&amp;trans=off">

> Database status
> State Approximate #results
> Ready to send 406,041
> In progress 2,157,840
> Waiting for validation 18
> Waiting to transition 1

Hello Josh,

We know, we can read the status page also. Please, you don't need to update this thread each minute. If we do want to know what is the status we can manage it to go and see by ourself.

Thanks for the update anyway.

> > Database status
> > State Approximate #results
> > Ready to send 406,041
> > In progress 2,157,840
> > Waiting for validation 18
> > Waiting to transition 1
>
> Hello Josh,
>
> We know, we can read the status page also. Please, you don't need to update
> this thread each minute. If we do want to know what is the status we can
> manage it to go and see by ourself.
>
> Thanks for the update anyway.
>--------------------
btw...as far as post outage database numbers go...we're coming out of this outage with more work units available than in the recent past...there's a pretty big stash still in the can...last couple times we looked at numbers like 38...8...or even zero at this stage...so 400,000 plus doesn't look too bad when you see it in that light.

---

PROUD TO BE TFFE!

> Ready to send 425,048
>
> What will happen if they run out?

<font>We will all wait patiently.</font>

---

> > Ready to send 425,048
> >
> > What will happen if they run out?
>
> We will all wait patiently.
>

Well I am all set now because I have a large queue! YAY!

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=1052&amp;prj=1&amp;trans=off">
<img src="http://seti.mundayweb.com/stats.php?userID=749&amp;trans=off">

> > > Ready to send 425,048
> > >
> > > What will happen if they run out?
> >
> > We will all wait patiently.
> >
>
> Well I am all set now because I have a large queue! YAY!

Did we need a half-dozen messages while you were obsessing over the lack of work?

---

> > > Ready to send 425,048
> > >
> > > What will happen if they run out?
> >
> > We will all wait patiently.
> >
>
> Well I am all set now because I have a large queue! YAY!
>-----------------
good for ya josh!...happy crunching!

---

PROUD TO BE TFFE!

Interesting...

---

Aloha, Uli