> last night's run is still running (that's about 14 hours). Memory > usage...454mb: > > 1642 ajack 30 15 454M 201M 154M R N 1.5 80.7 34:08 0 python >
Interestingly while still merrily tinkering along we see 545M... PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 1642 ajack 30 15 545M 167M 24440 D N 0.3 67.1 38:40 0 python ... what kinda of beastie is Gumpy? A hog, it seems... Ok, so maybe Python is as fluffy as Java w/ garbage collected object, and maybe Gumpy is greedy, but I can't see what would do this. The 'big stuff' (the build outputs) are kept in files, not memory. All that ought be in memory are the object (admittedly many) that represent the annotated run tree. 1) What is causing this? How does one introspect Python memory? 2) What was causing Gumpy to still be running @ 80% CPU 14 hours later? regard Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
