Comment 5 for bug 246891

Pelle Johansson wrote:
> It seems tailor was using a separately installed bazaar 1.2 due to
> importing the python lib directly. I am however using 1.5 for testing,
> and bzr upgrade did not want to do anything.
>
> I've tried upgrading using these formats:
> development (though I was not using bzr.dev)
> rich-root (took a whooping 11 hours to convert to)
> rich-root-pack
> back to default (from development)
>
> They all have pretty much the same performance, about 10 log messages
> every 4th minute.
>
> Does anyone have a clue why it is so slow, is it simply the large number
> of files?
>

Pelle,

Could you try collecting some profiling information for us on this?
Here's the command ...

  bzr --lsprof-file callgrind.out.logv log -v

You don't need to let it finish - you can Ctrl-C after a few minutes
and the profiling file should still be generated.

If you're running on Linux and are curious, you can view the output
file (callgrind.out.logv) using kcachegrind. Otherwise, please attach it
to the bug and we'll take a look.

Thanks,
Ian C.