Blitzed Again (Jul 02 2009)

No need for a trencher- go wireless.

Since connectivity on campus is provided by the IST department (the folks who brought you Cricket) they have to maintain it.

... and if there isn't a good clean line-of-sight from the lab to the right building(s) on Campus, then RF isn't a good choice.

ugh... my computers are dry.
____________

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

ugh... my computers are dry.

it's not the fact that the cpu is dry, it's the fact that the gpu's are dry..... 2 9400 gt's.... 32 sp each and they can run but probably won't finish a gpugrid wu.... cpu's are running, WCG,MW,ROSSETA, and a few others to keep them going.... i had those cpu do vtu@home but it(project leaders and servers have been unresponive as to why they were down for 2 weeks and i'm not crunching for them as i fear they will go down again....
____________

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

it's not the fact that the cpu is dry, it's the fact that the gpu's are dry..... 2 9400 gt's.... 32 sp each and they can run but probably won't finish a gpugrid wu.... cpu's are running, WCG,MW,ROSSETA, and a few others to keep them going.... i had those cpu do vtu@home but it(project leaders and servers have been unresponive as to why they were down for 2 weeks and i'm not crunching for them as i fear they will go down again....

i'll just go to the beta seti as their are 217,000 wu's waiting to be sent.....
____________

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

No need for a trencher- go wireless.

Since connectivity on campus is provided by the IST department (the folks who brought you Cricket) they have to maintain it.

... and if there isn't a good clean line-of-sight from the lab to the right building(s) on Campus, then RF isn't a good choice.

Screw LOS between the Lab and a campus building, is there LOS between the LAB and their ISP's node? (Calren?) Remove campus entirely. Get them an OC-768 link!

I see what you mean, but how about a system in which download servers are distributed around various universities (just split data and download to clients), whilst the ONLY functions that the Berkeley servers do is to receive all uploaded completed tasks, do validation, and result storage/archiving. Wouldn't that ease the bandwidth/server pain? Of course, there may be logistical problems in that the raw data disks from Aricebo would need to be sent out the different participating universities, but maybe this happens anyway for some observing projects.

Unfortunate for SETI, they do not have a "business model" because they are not a business - they are a science project.

I think there is merit to the idea of sharing the SETI@Home database to data servers across the Internet and leveraging the distributed servers' bandwidth. P2P networks are very good at demonstrating the power of collective bandwidth for spreading information from a single source :)

maybe, we should explore what drugdiscovery(A) and hydrogen(A) have done...... use 7zip to send files.... it makes 10 mb into 4-5 mb or less.

7zip works ok with boinc.... it will reduce the bandwidth a little. and may help with the congestion....

gamers also use it.... alot better at compressing than windows zip.
____________

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

maybe, we should explore what drugdiscovery(A) and hydrogen(A) have done...... use 7zip to send files.... it makes 10 mb into 4-5 mb or less.

Compression as been suggested before. But given the nature of the data, it's not very compressible.

maybe, we should explore what drugdiscovery(A) and hydrogen(A) have done...... use 7zip to send files.... it makes 10 mb into 4-5 mb or less.

Compression as been suggested before. But given the nature of the data, it's not very compressible.

It ought to compress fairly nicely, but there is a trade off with CPU time on the server to do the compression vs the transfer time to transfer the uncompressed bytes.

perhaps it should be beta tested on the seti beta...... just a 1-2 week trial... it couldn't hurt.... may loose a little time if it doesn't pan out, but it would be an option explored...
____________

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/
Go Georgia Tech.

maybe, we should explore what drugdiscovery(A) and hydrogen(A) have done...... use 7zip to send files.... it makes 10 mb into 4-5 mb or less.

Compression as been suggested before. But given the nature of the data, it's not very compressible.

It ought to compress fairly nicely, but there is a trade off with CPU time on the server to do the compression vs the transfer time to transfer the uncompressed bytes.

I'm not so sure about compression. My understanding was that random noise wouldn't compress very much at all as there are no patterns in it to exploit to compress. Now a WU with a signal might compress because of the pattern of the signal.