Everyones else machines are trying to contact the Servers and that is what Boinc was designed to do. If you let it do it in its own way things should be fine.

Ok
I will let my computer to manage itself.
But isn't it a problem if it contact server all the time for upload?
Not for me, it's just generate lots of error message pages. but for SETI server?

Regards.

Perhaps they could make a changed to the client app. When it gets one of the "Internet access OK - project servers may be temporarily down." then it could back off all the uploads instead of just the single one. Seems like that would DDOS the servers a bit less.

---

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

Everyones else machines are trying to contact the Servers and that is what Boinc was designed to do. If you let it do it in its own way things should be fine.

Ok
I will let my computer to manage itself.
But isn't it a problem if it contact server all the time for upload?
Not for me, it's just generate lots of error message pages. but for SETI server?

Regards.

Perhaps they could make a changed to the client app. When it gets one of the "Internet access OK - project servers may be temporarily down." then it could back off all the uploads instead of just the single one. Seems like that would DDOS the servers a bit less.

Actually those changes are being discussed at the Developer Level. Cuda being the animal it is and the outage here has proven that changes need to happen.

---

Please consider a Donation to the Seti Project.

Everyones else machines are trying to contact the Servers and that is what Boinc was designed to do. If you let it do it in its own way things should be fine.

Ok
I will let my computer to manage itself.
But isn't it a problem if it contact server all the time for upload?
Not for me, it's just generate lots of error message pages. but for SETI server?

Regards.

Perhaps they could make a changed to the client app. When it gets one of the "Internet access OK - project servers may be temporarily down." then it could back off all the uploads instead of just the single one. Seems like that would DDOS the servers a bit less.

Actually those changes are being discussed at the Developer Level. Cuda being the animal it is and the outage here has proven that changes need to happen.

That's good to know. If there is a beta app with any of these new "improvements" out soon I could toss it on a box or two in my test lab at work if more guinea pigs are needed.

---

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

Everyones else machines are trying to contact the Servers and that is what Boinc was designed to do. If you let it do it in its own way things should be fine.

Ok
I will let my computer to manage itself.
But isn't it a problem if it contact server all the time for upload?
Not for me, it's just generate lots of error message pages. but for SETI server?

Regards.

Perhaps they could make a changed to the client app. When it gets one of the "Internet access OK - project servers may be temporarily down." then it could back off all the uploads instead of just the single one. Seems like that would DDOS the servers a bit less.

Actually those changes are being discussed at the Developer Level. Cuda being the animal it is and the outage here has proven that changes need to happen.

That's good to know. If there is a beta app with any of these new "improvements" out soon I could toss it on a box or two in my test lab at work if more guinea pigs are needed.

Rom does not have Boinc Alpha currently open to new testers.

You can view the current discussions here http://lists.ssl.berkeley.edu/pipermail/boinc_dev/ Select "Subject" and the look for Optimizing Uploads

---

Please consider a Donation to the Seti Project.

Upload server is down again.

---

I made a small change that tripled our upload bandwidth. The change is to quickly drop excess connections rather than let them wait in the TCP queue.



We were doing this last week, but apparently Matt turned it off. IDK why. Matt is on vaca now.

---

Thank you Eric! Good, short, technical, and descriptive update.

Yes, thanks Eric. Very informative.....and I love the live bandwidth monitor image ;) ...very sexy.

---

I am TCP JESUS...The Carpenter Phenom Jesus....and HAMMERING is what I do best!
formerly known as...MC Hammer.

I made a small change that tripled our upload bandwidth. The change is to quickly drop excess connections rather than let them wait in the TCP queue.

We were doing this last week, but apparently Matt turned it off. IDK why. Matt is on vaca now.

Cool beans! I nearly had a heart attack when I saw things uploading again. lol

and who let Matt have a vacation? :)

---

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

I made a small change that tripled our upload bandwidth. The change is to quickly drop excess connections rather than let them wait in the TCP queue.

[snip]..................

We were doing this last week, but apparently Matt turned it off. IDK why. Matt is on vaca now.

Well.........there you go.........Matt is the one to blame!!

LOL

Uploads are moving into Berkeley. Changing my avatar to the nice alien.

---

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

Uploads are moving into Berkeley. Changing my avatar to the nice alien.

Aww man! I liked the red eyes and devil horns! They look cool! :)

---

I am happy now. My main machine just reported about 400 or so WU's.....only about another 400 or so to go by the look of things, then I can start downloading new work again.

I am on the road to recovery.....well, this system anyways.

---

I am TCP JESUS...The Carpenter Phenom Jesus....and HAMMERING is what I do best!
formerly known as...MC Hammer.

I made a small change that tripled our upload bandwidth. The change is to quickly drop excess connections rather than let them wait in the TCP queue.

[snip]..................

We were doing this last week, but apparently Matt turned it off. IDK why. Matt is on vaca now.

Well.........there you go.........Matt is the one to blame!!

I was going to blame Misfit.

---

I am happy now. My main machine just reported about 400 or so WU's.....only about another 400 or so to go by the look of things, then I can start downloading new work again.

I am on the road to recovery.....well, this system anyways.

I've not bothered to count all the wu's I have for uploading, but my total is down to about 230mb of space seti@home is using across my machines. I don't want to think about what all my machines at work have stored on them lol.

---

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

I would presume that someone sent a email that caughts Eric's attention.

I am happy now. My main machine just reported about 400 or so WU's.....only about another 400 or so to go by the look of things, then I can start downloading new work again.

I am on the road to recovery.....well, this system anyways.

It looks like the major portion of the rush has been dampened a bit.

Regards

---

Please consider a Donation to the Seti Project.

I made a small change that tripled our upload bandwidth. The change is to quickly drop excess connections rather than let them wait in the TCP queue.

<image removed>

We were doing this last week, but apparently Matt turned it off. IDK why. Matt is on vaca now.

Clearly it helps. Thanks for linking to Cricket so we can watch how it changes.

---

I've not bothered to count all the wu's I have for uploading, but my total is down to about 230mb of space seti@home is using across my machines. I don't want to think about what all my machines at work have stored on them lol.

I was just looking through the message log and got excited....lol

On this machine, on a 22" monitor @ 1680x1050 res, I have noticed that I am averaging 1 FINISHED result per complete vertical feed of text on the screen.....lol.

It's gonna be a while, but atleast it's finally moving.

---

I am TCP JESUS...The Carpenter Phenom Jesus....and HAMMERING is what I do best!
formerly known as...MC Hammer.

The interesting part is when it gets below critical mass and the requests work. Over the years have also found it interesting is how Boinc is better at "guessing" when to retry and be successful.

I've not bothered to count all the wu's I have for uploading, but my total is down to about 230mb of space seti@home is using across my machines. I don't want to think about what all my machines at work have stored on them lol.

I was just looking through the message log and got excited....lol

On this machine, on a 22" monitor @ 1680x1050 res, I have noticed that I am averaging 1 FINISHED result per complete vertical feed of text on the screen.....lol.

It's gonna be a while, but atleast it's finally moving.

---

Please consider a Donation to the Seti Project.

Well I see there are a lot of uploads going through (cricket, and server status page shows a large number of "received in last hour"), so I know uploads are going through. Every time I try, I get an instant "http error" and the exponential backoff occurs. I'll just leave networking suspended for more time.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I made a small change that tripled our upload bandwidth. The change is to quickly drop excess connections rather than let them wait in the TCP queue.

Ah, that would explain why some of my uploads are going through, and others are timing out after a second or less.

---

Grant
Darwin NT