Okay, panickers, what say you now?

MB ready to send is now upward of 245,000, still with only 6 splitters running. (FWIW, AP ready to send is about 2,000 with all its splitters running.)

Can we still say the MB/PFB splitters can't keep up with demand? Or is something else going on that's been causing the ready number to be so low recently?

Not convinced. They had real problems when (a) no AP was available, and (b) the MB work was mostly shorties. They are keeping up now with a better ratio of long/short MB tasks and the AP tasks. For example, I've received 364 tasks in the last 24 hours per BOINCTasks (staying at limits for the period). That number was ranging from 700 to 800 when we got almost all shorties, no AP, and the ready to send was depleted. Maybe there was a fix, but I'll wait and see.

I am wondering if they were perhaps stress testing the new pfb splitters. Then again it could have been since the number of results & wu's to purge had reached such a large number the creation rate was being limited to prevent the db choking again.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I suspect nothing has really been changed.

I will chalk it up to the changeover from shorties to longer running MB workunits, and the addition of AP work going out that keeps some GPUs busy doing AP rather than MB work.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Hmmm, strange
I have two computers, both running Windows 7 sharing the same internet connection. Since today's outage one has been giving "Scheduler request failed: HTTP internal server error" every time it tries to connect, the other one connects, uploads, downloads and reports very smoothly.
The only difference I can see is the one that fails is trying to report over 100 tasks, while the one that succeeds is doing a handful at a time....

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Hmmm, strange
I have two computers, both running Windows 7 sharing the same internet connection. Since today's outage one has been giving "Scheduler request failed: HTTP internal server error" every time it tries to connect, the other one connects, uploads, downloads and reports very smoothly.
The only difference I can see is the one that fails is trying to report over 100 tasks, while the one that succeeds is doing a handful at a time....

I connected once (no tasks) and haven't connected since. Also I can't get to my tasks page. Cricket says all is not well.

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

I'm getting can't connect to server. Looked at the cricket and it looks like someone put a 100meg limit on it!

---

I have two computers, both running Windows 7 sharing the same internet connection. Since today's outage one has been giving "Scheduler request failed: HTTP internal server error" every time it tries to connect....

All of mine are doing the same. All have over 100 tasks to report.

---

Reports are O.K. here but dont get new work.

---

With each crime and every kindness we birth our future.

And now the bun fight has begun ...

---

Things are starting to move here now.

Cheers.

Looks like the limit came off the link and we peaked at a hair over 500 meg.

---

Gary Charpentier wrote:

Looks like the limit came off the link and we peaked at a hair over 500 meg.

And look at the dip in the graph before the peak, 90 Mbits/sec ghost traffic. I don't think that is an offsite backup running.

As stated the normal upload traffic should be 150 Mbit/sec, but it's closer to 250. SETI@home is alone on that router and there wasn't any traffic before SETI@home.

Something is generating a constant 90 Mbits/sec 24/7.

As stated the normal upload traffic should be 150 Mbit/sec, but it's closer to 250. SETI@home is alone on that router and there wasn't any traffic before SETI@home.

Not to be picky, but...
That graph looks at the link from the router TOWARDS the Seti@Home servers, so the blue line is actually uploads and Scheduler Requests (out of the router), and the green wall is downloads and other outgoing traffic (into the router).

So Downloads run 150-250 MB/s and Uploads run 20-25 MB/s.

---

Donald
Infernal Optimist / Submariner, retired

Hmmm...
No stats export today.

Hope they did not forget to restart something.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I suspect nothing has really been changed.

Nope.
It's just a case of reduced demand allowing the ready-to-send buffer to refill- the maximum rate for splitting is still around 30/s, which isn't enough most of the time.

---

Grant
Darwin NT

As stated the normal upload traffic should be 150 Mbit/sec, but it's closer to 250. SETI@home is alone on that router and there wasn't any traffic before SETI@home.

Not to be picky, but...
That graph looks at the link from the router TOWARDS the Seti@Home servers, so the blue line is actually uploads and Scheduler Requests (out of the router), and the green wall is downloads and other outgoing traffic (into the router).

So Downloads run 150-250 MB/s and Uploads run 20-25 MB/s.

Yes, you are picky. I was talking about the project's upload. It doesn't matter what you call it, there's still ghost traffic.

Yes, you are picky. I was talking about the project's upload. It doesn't matter what you call it, there's still ghost traffic.

I think that may be the effect of some people who are still having communication problems with the servers catching up with their downloads.

Cheers.

As stated the normal upload traffic should be 150 Mbit/sec, but it's closer to 250. SETI@home is alone on that router and there wasn't any traffic before SETI@home.

Not to be picky, but...
That graph looks at the link from the router TOWARDS the Seti@Home servers, so the blue line is actually uploads and Scheduler Requests (out of the router), and the green wall is downloads and other outgoing traffic (into the router).

So Downloads run 150-250 MB/s and Uploads run 20-25 MB/s.

Yes, you are picky. I was talking about the project's upload. It doesn't matter what you call it, there's still ghost traffic.

Having spent 20+ years as a nuclear reactor plant operator/supervisor, 18 years after that as a machinery maintenance/repair tech/trainer, and many years working with computer systems, I must disagree - when talking technical issues, it DOES matter what you call it if you want to be understood.

Most of the regular posters here use the convention I listed - uploads TO the project From the cruncher, Downloads FROM the Project To the cruncher. Remember, too, that many more people read these discussions than participate in them, so not using the same terminology can cause confusion for them...

---

Donald
Infernal Optimist / Submariner, retired

Yes, you are picky. I was talking about the project's upload. It doesn't matter what you call it, there's still ghost traffic.

I think that may be the effect of some people who are still having communication problems with the servers catching up with their downloads.

Cheers.

And/or one or more of the servers did not come back online properly when the outage ended about noon local, and it took until about 1430 local to get it sorted......

---

Donald
Infernal Optimist / Submariner, retired

All is working well here at present, although Boincstats still has not received a stats dump since Monday.

Perhaps it will kick off at the usual time this afternoon.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

All is working well here at present, although Boincstats still has not received a stats dump since Monday.

Perhaps it will kick off at the usual time this afternoon.

The dump files are still currently dated Monday "06-May-2013 16:19". So in a few hours we shall see if they are updated.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[