Hi, I already reported the problem with history re-generation and now I have little bit more information on the issue: I am using latest 0.6 binaries with svn 1.4 on windows 2003.
The problem that when svn history is regenerated svn log is issued with the option --stop-on-copy (or it's java client analog) and thus there is no history of the files or the folders in the "just created" branches. This is not the case when the historycache is created together with indexing - all the history is in places, however the problem in this case, theat history of every file is built separately, and it brings very serious performance impact to the indexing process: it takes me less than 10 hours to index my sources without history but with svn history - it takes more than a week on the same machine. svn access is very good on my platform, it is central repository used by the dev.team - however very first revisions are really huges - and svn log takes several minutes and also we have more than 35.000 revisions already. I would recommend to redo the svn log mechanism, at least to cache in memory commit message and files changed per revision/repo - to not call it over and over again. Thanks, Moisei -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/opengrok-discuss/attachments/20080330/1745daf5/attachment.html>
