[Chicago] Out of Memory: Killed Process: on CentOS

Brian Ray bray at sent.com
Mon Apr 27 19:04:30 CEST 2009

On Apr 27, 2009, at 11:51 AM, David Beazley wrote:

>> If it's simply that cElementTree is keeping huge structures in memory
>> and you're getting too many concurrent requests for your RAM, move to
>> a SAX style API (state machine).
> Also look at the ElementTree.iterparse() function.  If you use that  
> in a clever way, you get all of the benefit of ElementTree plus the  
> memory savings of SAX (basically you can iteratively rip through XML  
> data and throw away the parts you're done with as you  go).

I will take a look at that.  I wonder how would be best to prove or  
dis-prove improvement's once I try that.

Thanks, Brian Ray

More information about the Chicago mailing list