On Tue, Apr 15, 2008 at 2:59 PM, eg <egoots_at_gmail.com> wrote:
> Branko Čibej wrote:
>
> >
> > >
> > > If you're already turning everything upside-down, and willing to trade
> > > memory for performance, it might be worth thinking about an optional
> > > svn-client-daemon that uses
> > > inotify/FSEvents/FindFirstChangeNotification/etc. Then you'd only have
> > > to do a full scan once per boot; the OS would tell you about any
> > > further modifications.
> > >
> > >
> >
> > Ouch. This introduces a long-living daemon that all other bits depend on,
> that has to be stable and never make a mistake. Not a good way to design
> robust software, IMHO. This falls under the "unnecessary complexity" and
> "premature optimization" headings. I'm convinced that a disk scan can be
> made orders of magnitude faster than ours is now, even without FS-specific
> tricks (like, e.g., walking the $MFT on NTFS)
> >
> >
>
> Agreed.
> Isn't Mercurial, with their revlog format, an example of an implementation
> which demonstrates this ability to be much faster for these type of
> operations.
Totally unrelated.
--dave
--
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
Received on 2008-04-16 19:12:35 CEST