Don't forget that we are already using machines with thousands of nodes and so to really benefit from something like boinc you would have to do quite a bit better than this.
And if more than one of us were to do it, we would be competing for resources with each other, not to mention the other interesting (non-go related) projects we would be competing with in order to utilize those resources. - Don On Thu, 2008-10-02 at 16:19 -0500, Zach Wegner wrote: > On Thu, Oct 2, 2008 at 3:48 PM, steve uurtamo <[EMAIL PROTECTED]> wrote: > > The networking issue is somewhat more serious. > > Not the actual network delay, but the mechanism > > that the boinc client software uses to process work requests > > and the interval at which people typically send > > back their results is such that you'd be unlikely to > > get a single work request back until after you needed > > it. > > This makes the assumption that boinc is used, or at least that one > central server is used. I've thought a lot about this issue, and I > think one central server would be too inefficient. I would use a > distributed network, and let each computer just connect with a small > number of others, creating something more like a web than a tree. This > could be optimized for ping time as well--arrange the nodes in the web > so that they talk most with those close to them. > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
