[computer-go] Pay-as-you-go cluster?

[steve uurtamo]

> It is not
> trivial to  
> distribute a
> number of jobs and then decide which of those jobs
> you can do without.

just consider it a noisy data channel that's
trying to give you a fixed-size packet of
information per send/receive cycle.  something
like an ECC will work here.

by slightly overlapping sections of your requests
to your end-nodes, you should be able to handle
an arbitrary (but bounded) variance in the amount
of noise/dropped data per send/request cycle.

the schedule for redundant data that you'd need
to request is a quick calculation per cycle, so
there isn't much overhead there.

s.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com