Author asnakelover
Recipients asnakelover, brian.curtin, pitrou
Date 2009-12-10.22:54:34
SpamBayes Score 5.74287e-07
Marked as misclassified No
Message-id <1260485677.82.0.178769470321.issue7471@psf.upfronthosting.co.za>
In-reply-to
Content
The gz in question is 17mb compressed and 247mb uncompressed. Calling
zcat the python process uses between 250 and 260 mb with the whole
string in memory using zcat as a fork. Numbers for the gzip module
aren't obtainable except for readline(), which doesn't use much memory
but is very slow. Other methods thrash the machine to death.

The machine has 300mb free RAM from a total of 1024mb.

It's not a new issue, I didn't find it when searching python bug
archives for some reason but google:

http://www.google.com/search?q=python+gzip+slow+zcat

It's an issue which people have stumbled into before but nobody seems to
have made headway any headway (I expect they just forked and called zcat
or gzip, like I did...).

It's a minor point since it's so easy to work around, in fact I have my
IDS system completed already - thank you so much python for being so RAD
friendly - yet the module is worthless if a user has zcat/gzip c
programs and knows they exist as it stands.
History
Date User Action Args
2009-12-10 22:54:37asnakeloversetrecipients: + asnakelover, pitrou, brian.curtin
2009-12-10 22:54:37asnakeloversetmessageid: <1260485677.82.0.178769470321.issue7471@psf.upfronthosting.co.za>
2009-12-10 22:54:36asnakeloverlinkissue7471 messages
2009-12-10 22:54:34asnakelovercreate