Comment 2 for bug 1301124

I think something else may be going on here. As a baseline: I just did some profiling of UTAH locally. It takes about 18M just right at startup (ie before its done anything) - so I think this may be the basic cost for us to load our code and python libraries.

I looked here:

 http://ci.ubuntu.com/memory/idle/arch/amd64/machine/2/install/results/desktop/pss/

And you can see that our measurements have suddenly gone down from about ~300M total to ~70M. Even on the 300M runs, I see this one:

 http://ci.ubuntu.com/memory/idle/arch/amd64/machine/2/install/result/19128/details/

where Utah still used about 18M. There's not a direct link, but if you click on the utah python links in the URLs I've listed, you'll get a javascript pop-up with the UTAH memory history. It looks like its about 18M and this 76M was an outlier.

Not to put this on a tangent: but can anyone explain this massive total memory drop?