Adding memory info to "usertest"

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian Clatworthy wrote:
> John Arbash Meinel wrote:
> 
>> So I'd like to get some ideas about how you think it would be good to
>> incorporate it. I'm wondering if peak memory measurements should be part
>> of every run, or if it should be a separate set of 'memory benchmarks'
>> that we run.
> 
> I think that's a great idea.
> 
> If there's a performance overhead to collecting the memory figures, I'd
> make it a separate run. Otherwise we can do it all at once and produce
> either a single report or maybe two reports: one for times, one for memory.
> 
> Ian C.
> 

I wouldn't expect there to be a performance overhead. If we were only
testing bzr, then we could just run all the commands with "-Dmemory" and
it would print the peak memory to stderr? when it finishes.

However, if you want to test across programs, then I would think we
would want to poll at a reasonable interval, say every 100ms. That can
be done in a thread in the main process, as long as it can be told what
pid to poll...

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrcdl4ACgkQJdeBCYSNAANBKACfW6vwVYY/WDz3N3TbLtK4vnrC
ECcAn2j1SeIGfId7F2GEWkMJGr+CLm6S
=JJXQ
-----END PGP SIGNATURE-----