CPUs have big caches to move the code closer to the data (well a copy of the data anyway).
Closeness in general is good, the question is what to move and how :-) Dave 2010/10/15 Julius Schmidt <a...@phicode.de> > Perhaps I'm getting this all wrong, but to me this seems like an > interesting idea, especially if you consider the impact of being "near > the files" on some classically considered computationally stressy tasks > like compiling (esp. with kencc). So moving the code near the data > definitely seems worth trying. > > aiju > > > > On Fri, 15 Oct 2010, Latchesar Ionkov wrote: > > There are definitely cases when moving the code instead of the data >> makes sense. But that discussion is mostly unrelated to the one on how >> to make the file I/O work better over high-latency links. >> >> 2010/10/15 erik quanstrom <quans...@quanstro.net>: >> >>> On Fri Oct 15 12:33:19 EDT 2010, lu...@ionkov.net wrote: >>> >>>> What if the data your process needs is located on more than one >>>> server? Play ping-pong? >>>> >>> >>> one either plays ping pong with the process or data. one >>> could imagine cases where the former case makes sense. >>> >>> - erik >>> >>> >>> >>
