[Mailman-Developers] Subscribers suddenly"disappear"

[Barry Warsaw]

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

On Aug 8, 2008, at 5:41 PM, A.M. Kuchling wrote:

> On Fri, Aug 08, 2008 at 04:58:07PM -0400, Barry Warsaw wrote:
>>> recursive or a complicated graph.  One experiment would be to  
>>> create a
>>> list with, say, 100,000 random foo at example.com addresses and  
>>> benchmark
>>> how much time it takes to unpickle it.  I'll try to do that tomorrow
>>> on a real computer (not this laptop).
>>
>> Hi Andrew, any results?
>
> The simple test program I used is below.  For a list with 89531
> addresses, the config.pck file is 9248317 bytes = 8.9M.  Doing ten
> loads and then ten saves in a row, the average load time is 1.36sec
> and the average save time is 4.5sec.
>
> This is on a development server here at Matrix, which has two 1.1GHz
> Intel CPUs and 2Gb of RAM; a respectable machine, but not what you'd
> currently use for a server.  So I think pickle really is pretty fast.
> Of course, if you had your Mailman installation on a busy mail or
> database server, all that I/O might kill you, but I think giving up on
> the mtime caching is not completely unreasonable.

Thanks for the feedback Andrew.

I don't know if it's worth changing for 2.1; I think it's a rare  
problem and the workarounds are now all in the archive.  It's probably  
worth changing for 2.2 (and is of course moot for 3.0), but it's still  
probably not worth making it configurable.  For 2.2, let's do the  
right thing and if we can make it fast in the meantime, great!

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSJy+inEjvBPtnXfVAQJiYgP+LPZABA78c604XzB39lBpkF/mfu/EEPE8
7aojEnqdaiorAA4PLQppAPNuF8oz9rQU87q/WVSJLdUo87HieTqddOy/CFwPJfYS
ixdJmc/k2TdnoLSFykcHhriJUQtfB1TNCodPG2BbFer7b4tEjyIRK11W6bC4gIM5
HfHYl1GLuck=
=ARJn
-----END PGP SIGNATURE-----