On Fri, Jan 8, 2010 at 3:50 PM, Bob Archer <bob.arc...@amsi.com> wrote: > >> I think the only way SVN can come close to acceptable performance >> for >> this use case (large file, lots of revs) would be to precompute and >> cache that data on the server side, so it has the data ready like >> CVS >> does. If anyone would implement this, I for one would be very happy >> :D. > > tortoise svn caches log data on the client. Of course, that doesn't help you > if you don't use a windows client.
Thanks for the suggestion. Yes that helps for "svn log" (however, we try to do everything from our IDE, which is IntelliJ, and it's svn plugin doesn't have such a feature). Also, our build tools, which use just the native command line client, suffer from the same problem of slow log. I don't think it helps for blame, as far as I tried. I also tried with a web viewer like FishEye, which is supposed to cache line-change and log data in a database. However, it also choked massively on this big file with lots of changes (and it's not really practical to open such a big file in a browser). Regards, Johan
