On Oct 22, 2008, at 12:15 PM, Andrew wrote: > Please ignore this mail. It was running without -H option. > Sorry for confusing you. >
I created bug 4154 to make opengrok automatically create the full history cache for "new" repositories.. Cheers, Trond > On Wed, Oct 22, 2008 at 11:48 AM, Andrew <yourmajestyi at gmail.com> > wrote: >> Hello, >> I would like to reopen this thread. >> In version 0.7 open grok calls "svn log --xml -v <FILE>" for every >> file it is indexing. >> *** This is super not efficient way to obtain the history. *** >> I am not sure it will ever work on any serious production repository >> (on my platform it is running 5 days already >> and it is not even close to the end). >> >> Concrete, there are two things that are wrong: >> 1/ (seems easy to fix) svn log should be called with --stop-on- >> copy parameter. >> 2/ (more complicate) it should not retrieve the history of every >> file >> from the server because svn log is revision oriented >> and revision normally contains several files, so it performs the same >> calls to the svn repository over and over again. >> >> Let's me try to be even more specific: our repository contains few >> revisions that consist of several tens thousands of files >> (they were imported from the previous version control system). >> It takes tens seconds to just bring all the data about this revision >> because the XML is just huge. >> And open grok attempts to bring this revision for almost every file >> because most of the files were "created" in this revision. >> >> Thanks, >> Moisei. >> > > > > -- > Best Regards, > Moisei -- Trond Norbye Database Technology Group E-mail: Trond.Norbye at Sun.Com SUN Microsystems Phone: +47 73842100 Haakon VII's gt. 7B Fax: +47 73842101 7485 Trondheim, Norway
