Loggerhead performance problem (Was: Re: Describe your workflow)

[Colin D Bennett]

On Thu, 26 Jun 2008 12:36:51 -0300
"Martin Albisetti" <argentina at gmail.com> wrote:

> On Thu, Jun 26, 2008 at 2:18 AM, Colin D Bennett <colin at gibibit.com>
> wrote:
> > bzr at deagle /bzr $ ls -l .bzr/loggerhead-files/
> > total 4035
> > -rw-r--r-- 1 bzr bzr  347136 Jun 10 22:58 changes.sql
> > -rw-r--r-- 1 bzr bzr 1508352 Jun  9 13:20 filechanges.sql
> > -rw-r--r-- 1 bzr bzr   46080 Jun 10 22:59 textindex-recorded.sql
> > -rw-r--r-- 1 bzr bzr 2217984 Jun 10 22:59 textindex.sql
> 
> This is odd, those cache's shouldn't be generating anymore with trunk,
> *just* filechanges.sql.
> Are you using trunk?
> Also, it looks like they are a few weeks old, so they may not be used.
> Can you delete them, restart Loggerhead, browse around and see if
> filechanges.sql does get generated?

Yes, I noticed the age of the files and forgot to mention it.  Clearly
they are not getting updated.

I deleted ``/bzr/.bzr/loggerhead-files``, restarted loggerhead, and it
did not recreate them.  Performance was the same, as expected.

====

Next, I moved the 'cachepath' into one of the branch sections of
loggerhead.conf.  This made that branch faster after I browsed the
'changes' pages once.  Each page seemed to be slow the first time, but
after that, the page was fast.  It is much nicer. :)

Is there any way to get loggerhead to cache things at the shared
repository level?  It's not a deal breaker, since it looks like I
already need to specify each branch explicitly in loggerhead.conf.

Thanks for the help!  I'm glad I gave loggerhead another chance.

Cheers,
Colin