Branch.lock_read() rather expensive

[Robert Collins]

On Sun, 2005-10-16 at 12:16 +1000, Martin Pool wrote:
> The policy is meant to be this:
> 
>  - Read locks are never required, because they can't be enforced over http
> 
>  - Read locks turn on caching of some objects in memory, so they can
> make operations faster and give repeatable reads.  It's a good idea to
> take and release the locks at a high level so that the cache is
> effective and so there's not too much overhead.  Typically this should
> be just below the command level.

And further to that, *nested* read_lock calls should be for all intents
and purposes, free. If they aren't, its a bug.

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051016/faacb4f9/attachment.pgp