Present batch of Shorties is sure maxing out the pipe.

Dave

I just dumped Vista and went back to windows XP. Updated everything, installed BOINC...so far so good.. Then CUDA units were completing in 4-5 minutes! Thought for sure something was messed up but apparently not if your getting shorties too.

I was about to reinstall BOINC.. Anyway, thanks for mentioning that. Saved me a lot of time and frustration.

30.01.2010 13:27:50 SETI@home Temporarily failed download of ap_01ja07ae_B5_P0_00193_20100129_23450.wu: HTTP error
30.01.2010 13:27:50 SETI@home Backing off 1 hr 21 min 8 sec on download of ap_01ja07ae_B5_P0_00193_20100129_23450.wu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
get two astropulse, but second hung up....
any ideas

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;ranges=d%3Aw%3Am%3Ay;view=octets has been pegged near the top for the last 18 hours or so, and has been higher than recent average for the last few days.

This is probably due to the combination of the return of Astropulse, combined with another run of "shorties". Best advice is probably to just be patient.

[edit]
Those graphs are Berkeley local time (PST), not UTC.

http://fragment1.berkeley.edu/newcricket/grapher.cgi?target=%2Frouter-interfaces%2Finr-250%2Fgigabitethernet2_3;ranges=d%3Aw%3Am%3Ay;view=octets has been pegged near the top for the last 18 hours or so, and has been higher than recent average for the last few days.

This is probably due to the combination of the return of Astropulse, combined with another run of "shorties". Best advice is probably to just be patient.

[edit]
Those graphs are Berkeley local time (PST), not UTC.

Yup.
The crickets are chirping at warp speed again........

---

"Time is simply the mechanism that keeps everything from happening all at once."

This is probably due to the combination of the return of Astropulse, combined with another run of "shorties". Best advice is probably to just be patient.

Agreed on all counts. I got an allocation of 50 shorties in one request a while back, so I've been down in the crunch farm watching how the improved backoff/retry mechanism in the newer clients handles the clogged pipe (first real test for a long time). Looks pretty good to me.

This is probably due to the combination of the return of Astropulse, combined with another run of "shorties". Best advice is probably to just be patient.

Agreed on all counts. I got an allocation of 50 shorties in one request a while back, so I've been down in the crunch farm watching how the improved backoff/retry mechanism in the newer clients handles the clogged pipe (first real test for a long time). Looks pretty good to me.

I got a real good cache on all 3 Cuda rigs, so I am like 10 days or more behind the curve on this one.....

I absolutely hate the way the newer clients handle a clogged pipe. The 'project backoffs' are a PITA.......

It's hard to even push the buttons enough to get them to push up and downloads through when the servers got their undies in a bundle.

May be good for the servers, but it's hell for the clients.

At least the old versions will still chink away at the pending transactions and push them through one at a time as they can connect.

EDIT.....
And no, plinking the servers constantly is NOT my problem....
It is the SERVER'S problem.

Now we are up to the old 'bandwidth up the hill' argument.
I personally don't give one rat's ass about it, as long as the pipe stays tight at 100mbs or whatever it can do, I have as good a chance as anybody at connecting.
An upgrade would be nice, but would the servers be able to handle it then?

It's all a pig in a poke unless some real hard choices are made up the hill. And the money to implement them.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I absolutely hate the way the newer clients handle a clogged pipe. The 'project backoffs' are a PITA.......

It's hard to even push the buttons enough to get them to push up and downloads through when the servers got their undies in a bundle.

May be good for the servers, but it's hell for the clients.

At least the old versions will still chink away at the pending transactions and push them through one at a time as they can connect.

EDIT.....
And no, plinking the servers constantly is NOT my problem....
It is the SERVER'S problem.

Now we are up to the old 'bandwidth up the hill' argument.
I personally don't give one rat's ass about it, as long as the pipe stays tight at 100mbs or whatever it can do, I have as good a chance as anybody at connecting.
An upgrade would be nice, but would the servers be able to handle it then?

It's all a pig in a poke unless some real hard choices are made up the hill. And the money to implement them.

So, let me make sure I understand this.

If your sewer line is clogged, you solve the problem by walking around the house, turning on all the faucets, and flushing all the toilets.

Maybe inviting over friends and getting a keg of beer.

... and it isn't your problem if everything overflows.

Yet, if you were careful about using the drains, you'd save the floor, and could call the plumber during normal business hours and not pay extra.

Uploading and downloading? Same thing.

---

I absolutely hate the way the newer clients handle a clogged pipe. The 'project backoffs' are a PITA.......

It's hard to even push the buttons enough to get them to push up and downloads through when the servers got their undies in a bundle.

May be good for the servers, but it's hell for the clients.

At least the old versions will still chink away at the pending transactions and push them through one at a time as they can connect.

EDIT.....
And no, plinking the servers constantly is NOT my problem....
It is the SERVER'S problem.

Now we are up to the old 'bandwidth up the hill' argument.
I personally don't give one rat's ass about it, as long as the pipe stays tight at 100mbs or whatever it can do, I have as good a chance as anybody at connecting.
An upgrade would be nice, but would the servers be able to handle it then?

It's all a pig in a poke unless some real hard choices are made up the hill. And the money to implement them.

So, let me make sure I understand this.

If your sewer line is clogged, you solve the problem by walking around the house, turning on all the faucets, and flushing all the toilets.

Maybe inviting over friends and getting a keg of beer.

... and it isn't your problem if everything overflows.

Yet, if you were careful about using the drains, you'd save the floor, and could call the plumber during normal business hours and not pay extra.

Uploading and downloading? Same thing.

Sounds like a breaking the Lease Party I had many many years ago.....LOL

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Uploading and downloading? Same thing.

No......I just keep pissing up the rope and hope it does not trickle back down......
And hope whoever is holding the rope up top pulls it in.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I must admit to kicking things manually every time 1 of my offline clients wants a dump (so to speak).

I must admit to kicking things manually every time 1 of my offline clients wants a dump (so to speak).

Boy I have Never done that...(Watching out for Ned)LOL

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Your Welcome.

Dave

---

Uploading and downloading? Same thing.

No......I just keep pissing up the rope and hope it does not trickle back down......
And hope whoever is holding the rope up top pulls it in.

Interesting that you left out everything but the least interesting part.

Either analogy sounds like you're going to make a mess, and then have to deal with it.

---

Your Welcome.

Dave

I guess the shorties have run dry. All WU's are crunching in normal times now.

Rig on a Bench still has 870 to do at the moment.
At 1 every 45 secs that's another 11 hrs or so. LOL.

Dave

---

Rig on a Bench still has 870 to do at the moment.
At 1 every 45 secs that's another 11 hrs or so. LOL.

Dave

What are those puppies running at? Mine seem to be around 2 minutes each.

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Sorry for misinformation 4 GPU's so in 3 mins thats 1 every 45secs
Everything is stock here.

Dave

---

And no, plinking the servers constantly is NOT my problem....
It is the SERVER'S problem.

Now we are up to the old 'bandwidth up the hill' argument.
I personally don't give one rat's ass about it, as long as the pipe stays tight at 100mbs or whatever it can do, I have as good a chance as anybody at connecting.
An upgrade would be nice, but would the servers be able to handle it then?

It's all a pig in a poke unless some real hard choices are made up the hill. And the money to implement them.

The most cost-effective solution to the "plinking the servers" problem is to make a BOINC client that doesn't plink.

Same with your 100 megabit question (peak throughput is probably about 90 megabits). If the clients could tell that the wire was at 90 megabits and take turns more slowly then *throughput* would go up.

But BOINC features that do that (like the project-wide backoff) are widely condemned even though they do exactly what you say you want.

---

And no, plinking the servers constantly is NOT my problem....
It is the SERVER'S problem.

Now we are up to the old 'bandwidth up the hill' argument.
I personally don't give one rat's ass about it, as long as the pipe stays tight at 100mbs or whatever it can do, I have as good a chance as anybody at connecting.
An upgrade would be nice, but would the servers be able to handle it then?

It's all a pig in a poke unless some real hard choices are made up the hill. And the money to implement them.

The most cost-effective solution to the "plinking the servers" problem is to make a BOINC client that doesn't plink.

Same with your 100 megabit question (peak throughput is probably about 90 megabits). If the clients could tell that the wire was at 90 megabits and take turns more slowly then *throughput* would go up.

But BOINC features that do that (like the project-wide backoff) are widely condemned even though they do exactly what you say you want.

Maybe I did not state my case clearly.......

I do NOT want the client to do a project wide backoff when it feels it necessary.

I want it the plonk the servers anytime it needs to get work or report it.

I know this is hard on the servers and bandwidth....

But that is what I want. When the servers are in trouble and it takes a couple of DAYS to clear the ready to send buffer, it drives the kitties wild.

The older client will keep trying, one at a time, until things get through.
The newer client will just back off like a lazy stepchild, and quit even trying just because a few attempts don't make it.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I know this is hard on the servers and bandwidth....

But that is what I want.

That's what the [Retry Now] and [Update] buttons are for. Oh, too human labor intensive? Fair is fair... ;-)