Comment 26 for bug 118625

On Thu, 2009-11-19 at 21:59 +0000, Max Kanat-Alexander wrote:
> @stub: That was pretty much my thought as well. At first I'm just going
> to make sure that loggerhead only builds one revision cache at a time
> for any given branch, but if that doesn't fix it, then I'll make it only
> build one revision cache at a time globally (but I think that could
> seriously degrade performance on a major installation like codebrowse,
> so it's not the ideal solution).
>
> And yeah, due to the way Python threads work, at least on my local
> machine I only saw loggerhead use one core of my CPU no matter how
> loaded it was. (I've also proposed elsewhere that there be some
> rearchitecture to improve loggerhead's scalability, we'll see how that
> proposal goes.)

So, bzr's core is starting to release the GIL at various places -
building multiple caches will start to get concurrency with python
threads. (Maybe not awesome concurrency, but some).

-Rob