• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

This whole SETI bandwidth thing is really beginning to suck...

C

CraigRT

Lifer
There is almost 3000 work units queued to upload in OK's proxy, and there has been almost no progress in cracking.. caches are getting low, and if I keep uploading, it will just make situations worse, this really sucks.. I hope it is all over soon, I want my flowing WU's back!! 🙁
 
the reason why OK didn't flush all WUs at a time is to prevent a user_info.sah mix up problem.

if you have a queue running or use another queue with less traffic, the bandwidth problem ain't that bad after all.
 
I have been extremely lucky and been able to get my cache filled with ten and download what was there. But am holding 3 or more results on other computers. So I dont think I am in as bad a shape as many people here.
Sorry for all the misery though I have had it before as well.🙁
 


<< Sorry for all the misery though I have had it before as well. >>



It's not THAT much misery.. but it's disappointing.. I just wish something like this could happen to an unimportant project like OGR.. 😀
 


<< Luckily I have enough wu's cached to keep busy for 2 days. >>



I've got enough for like a week, but I want to flush more often so I can get new stuff in, and see some numbers.. :disgust:
 
Grin, You will see ... you will see. 😉

Congratulations on your 1st Seti Work Unit! 😀
 
Awwww... poor Yield. You want to SEE a yield from all your 'puters' hard work!!! lol 😛

And Grin...You have been assimilated. Resistance is futile.! 😀
 
I know man, I know.. 🙁

😀 hehehe

Well... maybe to make you feel better, I'm a babe. AND I do hot tubs every once in awhile! 😉 😛
(/me blushes and runs off behind the bushes...)
 


<< I know man, I know.. 🙁

😀 hehehe

Well... maybe to make you feel better, I'm a babe. AND I do hot tubs every once in awhile! 😉 😛
(/me blushes and runs off behind the bushes...) >>

ROTFL! 😀😀😀😀
 


<< Well... maybe to make you feel better, I'm a babe. AND I do hot tubs every once in awhile! 😉 😛
(/me blushes and runs off behind the bushes...) >>


/frantically searching for his pills... 😱
 


<< I know man, I know.. 🙁

😀 hehehe

Well... maybe to make you feel better, I'm a babe. AND I do hot tubs every once in awhile! 😉 😛
(/me blushes and runs off behind the bushes...) >>



:Q
 
Last night there must not have been to much band-width as one of my Queues is getting pretty full!:Q
 


<< if you have a queue running or use another queue with less traffic, the bandwidth problem ain't that bad after all. >>


That is not true for all of us as the past two days I've had a lot of trouble. I stopped sending my stuff to OK's site to ease his load a little bit. For the first week I was able get my stuff through to SETI with little problem. It would take me about 2 hours on dialup. Yesterday I was able to flush all my WUs, but it didn't refill the Queue completely. Well, this morning it ran for four hours and I still had 47 WUs to upload and was able to get only 15~20 WUs downloaded.

When this problem first started, many of the queues backed up that week, but were able to get caught up over the weekend. Since then the weekends have not been any better than the rest of the week. I really wonder if SETI has reached critical mass!?! Can they fix it and will they?

Here is what SETI says about it:

Short-term solutions We're working on several short-term solutions:

o Increase the bandwidth of UCB's network connection. We hope to "expand the pipe" by about 10 Mbps - enough to ease, but not eliminate, the crisis. The issue is money - bandwidth costs about $300 a month per megabit, and neither SETI@home nor the university has budgeted for this cost.

o Send data more efficiently. Currently work units are encoded as text. By sending them in binary, we can shrink them by about 25%. (Note: data compression isn't effective for our data, which is primarily random noise). This change will require a new version of the client software.

o Increase the amount of computation per work unit. Doubling the CPU time per work unit - by looking at more chirp rates, for example - will reduce bandwidth by 50%. There is scientific justification for doing this, although the law of diminishing returns applies. This will also require a new version of the client software. (This is what many of us are afraid will happen as it did in Jan 01.)

Long-term solutions
The long-term solution is to allow work units to be sent from servers outside UC Berkeley. This could be done, for example, by sending work units to servers at organizations - companies and universities - that are willing to donate part of their outgoing network bandwidth to SETI@home. In addition to solving the current problem, this could greatly increase our overall data capacity, enabling us to search for ET signals in a wider frequency band.

This solution represents a significant change to our software; we will use this approach in our next-generation software. We are seeking funding to develop this software, and it won't be ready for at least 6 months.

 
Also...........

To help us achieve a short-term solution, you can help in two ways:

Donate to SETI@home. This will enable us to buy network bandwidth.
Help us find "bandwidth sponsors". We hope that a major commercial ISP might donate bandwidth to UC Berkeley to help SETI@home. If you work for, or have contacts in, such a company, please contact us.
 


<< o Increase the amount of computation per work unit. Doubling the CPU time per work unit - by looking at more chirp rates, for example - will reduce bandwidth by 50%. There is scientific justification for doing this, although the law of diminishing returns applies. This will also require a new version of the client software. (This is what many of us are afraid will happen as it did in Jan 01.) >>



:|

All my fleet are currently running at 8hrs per WU or longer as it is. I don't know if I could stand 16 hours per WU for my fleet. 🙁
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top