Some positive feedback on the responsiveness of bzr(explorer)

[Eli Zaretskii]

> Date: Wed, 11 May 2011 10:44:34 +0300
> From: Alexander Belchenko <bialix at ukr.net>
> Cc: Bazaar <bazaar at lists.canonical.com>
> 
> > This set of observations was on WinXP (I should have mentioned that).  
> > And I'm actually not sure whether or how 'lazy' memory allocation is on 
> > WIn32.  Good question.  I suppose I should know.  I'll have to test that 
> > when I get a few minutes.
> 
> Which tools are you using to get such statistics? Process Explorer?

Process Explorer will do, but vmmap is even better.

According to a quick test, calling `malloc' causes an immediate
commit, even if the memory is not touched.  This is on XP with a toy C
program compiled with MinGW GCC and using MS runtime.

I don't know how that relates to what bzr does via Python, as I have
no idea how Python manages its memory in general and on Windows in
particular.  I can tell that Emacs on Windows reserves between 1GB and
2GB of heap on startup, but commits dynamically only as much as it
actually needs (and vmmap shows the uncommitted memory as "Reserved").
However, Emacs uses VirtualAlloc directly, bypassing `malloc' in MS
runtime.