This post from Matt seems pretty explicit to me ...

However that post was on March 8, the problems we're having occured about a week, week and a half after that.
If it is related to that post, it would be nice to have confirmation, as things were running OK with a ready-to-send buffer.

I suspect this shall either pass or become the new normal, although right now it is being brought to bear due to the shorties being sent out.

We are dealing with quite a different animal since the move to the new digs for the servers. The amazing bandwidth is a two edged sword. Cuts both ways.

It has allowed the servers to send and receive all the data possible in both directions most of the time. This is a very grand thing!

What has happened, is that now other limitations present themselves. Splitting capacity. Database capacity. I/O capacity.
Still, a very good thing.

What do you think is worse, not being able to get work because the servers could not parse it out over 100Mb bandwidth, or not being able to get work at times because the servers are handing it out as fast as they can feed it to the new pipe?

I vote for the current situation.

The day may well come when Eric or Matt have to post and say..'We have no more data from Arecibo to split today.'

And that, believe it or not, would be the best situation the project could be in.

---

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

I suspect this shall either pass or become the new normal, although right now it is being brought to bear due to the shorties being sent out.

Unfortunately it was also the case for several hours where there were hardly any shorties about.

---

Grant
Darwin NT

I suspect this shall either pass or become the new normal, although right now it is being brought to bear due to the shorties being sent out.

Unfortunately it was also the case for several hours where there were hardly any shorties about.

Well, either there is something left to be sorted, or this is just the way it shall be.

I am just now looking at the Killawatt on one of my best rigs. 350 watts.
It should be drawing about 650 watts. It will keep sniffing for work, and will get a hit here and there.

I DO still wish the limits were raised, would keep my fast crunchers in work for a bit longer when the ready to send crashes.

But, I am in the same boat as everybody else. And will keep rowing as hard as I can.

---

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

I belive the problem is the way the pfb_splitter works, seems they are slower than the old mb_splitter used until few days ago and the lack of AP work who makes we all asking for MB work only and some hidden limit added by Matt. Sooner or later we will know the answer. Until that is fixed our power bill would be smaller...

---

I DO still wish the limits were raised, would keep my fast crunchers in work for a bit longer when the ready to send crashes.

Even that wouldn't help in this case as the output isn't sufficient to meet demand, let alone produce a ready-to-send buffer.

Ideally, they'll sort out the splitters so they can maintain a ready-to-send buffer.
Then sort out the database issues so we can increase the limits so we can get enough work to last more than a couple of hours.


If we run out of work, we run out of work. I can live with that (it'd be disappointing, but if there isn't any to process then there's no point getting worked up about it).
But when there is work there to be done, but it's not available, that's frustrating.

---

Grant
Darwin NT

This post from Matt seems pretty explicit to me ...

However that post was on March 8, the problems we're having occured about a week, week and a half after that.
If it is related to that post, it would be nice to have confirmation, as things were running OK with a ready-to-send buffer.

No, Grant, it is from April 8, immediately after the move to the CoLo facility. We have been here less than 1 month, and for the last 2 weeks the data being split has been mostly shorties. Absent any new word from Matt, I must presume that those throttles he mentioned are still in place, and for the reasons he stated. We are still establishing the new "normal". As always with this project, patience is not just a virtue, it is a requirement.

Edit: added link to Matt's Tech News message.

---

Donald
Infernal Optimist / Submariner, retired

I just wish for what I came here for.
Un ending WUs for me to process in the name of the un endeding searrcy.

I have come and gone.

You can not sidetrack me any more.

Ya know, friends..........I been wrong as hell sometimes.
NOt on this one.

\Hit the road, Jack.
\

I really don't think some of you realize just who you really dealing with.

---

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

This post from Matt seems pretty explicit to me ...

However that post was on March 8, the problems we're having occured about a week, week and a half after that.
If it is related to that post, it would be nice to have confirmation, as things were running OK with a ready-to-send buffer.

No, Grant, it is from April 8, immediately after the move to the CoLo facility.

Typo on my part- i meant April. The rest of my statement in that post is correct.

---

Grant
Darwin NT

I really don't think some of you realize just who you really dealing with.

No one is any bit scared of you, so knock it off.

Can't seem to get any work for the GPU. Anyone else with the same issue?

---

Can't seem to get any work for the GPU. Anyone else with the same issue?

Nope.

"Project has no tasks available" is the usual response for any type of work request over the last week or so, then every now & then some work gets allocated. Depending on the backoffs for CPU or GPU work one or the other may miss out on that work allocation because it wasn't asked for due to the backoff.

---

Grant
Darwin NT

I really don't think some of you realize just who you really dealing with.

No one is any bit scared of you, so knock it off.

Can't seem to get any work for the GPU. Anyone else with the same issue?

I'm offline until 7pm, but this might explain the lack of work.

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-211/gigabitethernet6_17&ranges=d%3Aw&view=Octets

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I'm offline until 7pm, but this might explain the lack of work.

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-211/gigabitethernet6_17&ranges=d%3Aw&view=Octets

?

---

Grant
Darwin NT

I'm offline until 7pm, but this might explain the lack of work.

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-211/gigabitethernet6_17&ranges=d%3Aw&view=Octets

?

The wu output seems kind of low.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I'm offline until 7pm, but this might explain the lack of work.

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-211/gigabitethernet6_17&ranges=d%3Aw&view=Octets

?

The wu output seems kind of low.

That just shows network traffic.

This gives a better idea of WU generation.
http://setistats.haveland.com/cgi/munin-cgi-graph/setiathome/setiathome/sah_creation-day.png

and this shows you how much work is ready-to-send & how much is being returned per hour.
http://setistats.haveland.com/cgi/munin-cgi-graph/setiathome/setiathome/sah_results-day.png

---

Grant
Darwin NT

I'm offline until 7pm, but this might explain the lack of work.

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=/router-interfaces/inr-211/gigabitethernet6_17&ranges=d%3Aw&view=Octets

?

The wu output seems kind of low.

Work out is the blue line this represents the work been returned to the servers. I think this was sitting about normal 18.19 MB as I write, reason not why it has been so high yesterday Berkely time is because I think they were transferring more data sets to the servers for the splitters to be able to work on. As I write the bits in data been sent to clients is at 189.06 MB I don't consider this to be low unless it becomes under 100 MB.

---

Not so good here right now.
I have a few powerful rigs left sucking big wind for the lack of tasks sent.

---

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

Not so good here right now.
I have a few powerful rigs left sucking big wind for the lack of tasks sent.

Sorry guys ;)

04/05/2013 15:55:05 | SETI@home | Scheduler request completed: got 48 new tasks

Not so good here right now.
I have a few powerful rigs left sucking big wind for the lack of tasks sent.

Sorry guys ;)

04/05/2013 15:55:05 | SETI@home | Scheduler request completed: got 48 new tasks

The kitties gracefully sidestep so's Richard can get some work.

You are quite welcome, Richard.

Maybe my turn next.

And see/?
My big hitter just got a 51 WU hit.

Should be good to go for about 20 minutes or so...LOL.

---

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

Not so good here right now.
I have a few powerful rigs left sucking big wind for the lack of tasks sent.

Sorry guys ;)

04/05/2013 15:55:05 | SETI@home | Scheduler request completed: got 48 new tasks

I would occasionally get a burst of work units like that, but I spin through them rather quickly. Then there might not be anything for hours. There hasn't been any AP splitting for days.

The funny thing is that before they moved to the colo facility, I actually got more work units even with the retries, frustration and all.

---

Not so good here right now.
I have a few powerful rigs left sucking big wind for the lack of tasks sent.

Sorry guys ;)

04/05/2013 15:55:05 | SETI@home | Scheduler request completed: got 48 new tasks

I would occasionally get a burst of work units like that, but I spin through them rather quickly. Then there might not be anything for hours. There hasn't been any AP splitting for days.

The funny thing is that before they moved to the colo facility, I actually got more work units even with the retries, frustration and all.

Well, that's the breaks, as they say.

I am OK with the servers being all that they can be for now.

It's a nice change of pace for them at least being able to send what they can send.

The Cricket is doing a rather steady 200Mb/sec.....so work is flowing.

Much better than with the old 100Mb cap.

---

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