2009/11/17 Jon Schneider <jkschnei...@gmail.com> > > > If the index grows, accessing the index from a remote box may become > long. > > If you think big, you will have to find a way to transfer index updates > to > > the clients which is optimizing the network, such as transferring diffs > or > > something similar. But this becomes difficult to implement, unless you > want > > to rely on existing technology for that (such as a SCM). > > I am having trouble trying to manufacture a scalability problem here (with > my unscientific approach). I am up to 1,149 jars containing class types > with over 28,700 types in my test repository and the index is at 39 mb. > I've pushed the index out on a remote filesystem, and the quick search > opens the index in 219 ms. After the index reader is opened, subsequent > searches return in the microsecond range until the reader becomes stale > from > a commit and is reopened. > Yes, I think the main point is to "get" the index locally. At 39mb depending on your bandwidth to the remote server it can take time... and having to doanload the full index each time it is modified sounds scary. But maybe Nicolas has good things to share about that.
Xavier -- Xavier Hanin - 4SH France - http://www.4sh.fr/ BordeauxJUG creator & leader - http://www.bordeauxjug.org/ Apache Ivy Creator - http://ant.apache.org/ivy/
