bzr too slow

[John Arbash Meinel]

Denys Duchier wrote:
> John Arbash Meinel <john at arbash-meinel.com> writes:
> 
> 
>>It could be a few things. At one point, the hash-cache wasn't properly
>>flushing to disk, so it was having to read all files over again.
>>I thought Aaron submitted a fix for this, and it had been pulled in.
> 
> 
> but now the hashcache gets written on _every_ unlock operation, regardless of
> whether the lock is actually being released. what you'd really want to do is
> write it at the _last_ unlock.
> 
> Cheers,
> 
> --Denys

Well, that could certainly be a problem. But it isn't entirely true. It
only does so if the hash-cache says it is unclean. (If a file being read
had a new stat result).
Which means if you have never done a 'bzr status' before, it probably
will write a few too many times.
But after that, it will only happen when there have been actual changes
detected. Which seems reasonable.

And really means we need to see the --profile, to see what is really
happening.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060110/dae251ef/attachment.pgp