[Mailman-Users] Python process size grows 30x in 8 hours (memory

Mark Sapiro mark at msapiro.net
Thu Jul 3 05:15:31 CEST 2008


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

Barry Warsaw wrote:
| On Jul 2, 2008, at 11:01 PM, Mark Sapiro wrote:
|
|> The attached 'post' file is a modified version of scripts/post.
|
| Hi Mark, there was no attachment.


Yes, I know. I was just about to resend. It is attached here. The MUA I
used to send the previous message gives any attachment without an
extension Content-Type: application/octet-stream, so the list's content
filtering removed it.


|> It does the following compared to the normal script.
|
|> The normal script reads the message from the pipe from the MTA and
|> queues it in the 'in' queue for processing by an IncomingRunner. This
|> script receives the message and instead queues it in the 'bad' queue.
|> It then looks at the size of the 'bad' queue entry (a Python pickle
|> that will be just slightly larger than the message text). If the size
|> is less than MAXSIZE bytes (a parameter near the beginning of the
|> script, currently set to 1000000, but which you can change as you
|> desire), it moves the queue entry from the 'bad' queue to the 'in'
|> queue for processing.
|
| I'm not sure 'bad' should be used.  Perhaps a separate queue called
| 'raw'?  It is nice that files > MAXSIZE need only be left in 'bad'.


If we're going to do something like this going forward, we can certainly
change the queue. For this 'debug' effort, I wanted to keep it simple
and use an existing mm_cfg queue name.

- --
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFIbERTVVuXXpU7hpMRAtD3AJ4wak9befESKQlF3t2ZKos9W2WuTQCfbOCB
Yh9VIStJMHWfiLVlYjM5uoo=
=bU1+
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: post
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20080702/9c83b8ce/attachment.txt>


More information about the Mailman-Users mailing list