But I think the school has limited them to 18 gigabytes, if I remember
correctly, hence the increase in crunch time for a work unit . As for the
overload, I'll just let my client worry about it and when ever it can
automatically get one, it'll get one.
Allan
>
>
>
>
> S@H has a 30 gigabyte bandwidth.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> On Mar 1, 6:58pm, "chrisrutt" wrote:
> } Subject: Overloads and Digests Quotes
> }
> } . . .
>
> - - - - -
>
> Pardon me while I think (compute) out loud for a moment.
>
> There's about 86,400 seconds in a day. A 1Mbit/sec link
> (approximately a T1) can average 100Kbytes/sec (protocol,
> acks, etc...) That's about 8.6Gbytes/day.
>
> A WU takes about 340K to download. So the above link
> could handle about 25,000 WUs per day. 1.5 million WUs
> would take about 2 months.
>
> A typical 10Mbit network could cut that down to a week.
> A fast 100Mbit network could cut that down to 14 hours.
> Like I said, the first to get their WUs will likely be
> coming back for "seconds" before everyone has been fed.
>
> Anyone remember how fast the S@h link to the outside
> world is? (I'm not talking about the cut fiber, but the
> ultimate link to the internet).
>
> Of course, 20 WUs a piece would scale those numbers up
> accordingly.
>
> ==
> Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html
> This list sponsored by talkspace.net: building space communities online.
> Mailing list services provided by klx.communications -- www.klx.com
>
==
Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html
This list sponsored by talkspace.net: building space communities online.
Mailing list services provided by klx.communications -- www.klx.com
