Mailman does not generate a high load on my machine
![](https://secure.gravatar.com/avatar/c8e36f7bd676686e9e9577b1a1a5b771.jpg?s=120&d=mm&r=g)
Hello,
I send a e-mail a while ago saying mailman was causing a huge load on my server. That's not correct. I found out that it was a problem in the 2.2.11 version of the linux kernel. I'm with 2.2.12 now and its ok.
Sorry for the mess.
fc
-- riverrun.com.br / actech.com.br
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"FC" == Fabricio Chalub <chalub@actech.com.br> writes:
FC> I send a e-mail a while ago saying mailman was causing a huge
FC> load on my server. That's not correct. I found out that it
FC> was a problem in the 2.2.11 version of the linux kernel. I'm
FC> with 2.2.12 now and its ok.
Can you provide any more information? Do you know what specifically about the 2.2.11 kernel was causing the problem?
I've been closely monitoring python.org after installing Jeremy Hylton's pipermail performance improvements and I've been extremely happy. Python.org can now easily keep up with the traffic. Not to say there aren't more improvements possible, but the 80/20 rule definitely comes into play. The changes may be good enough to warrant a 1.1 release even before the I18N stuff gets merged in.
-Barry
![](https://secure.gravatar.com/avatar/c8e36f7bd676686e9e9577b1a1a5b771.jpg?s=120&d=mm&r=g)
Actually no. :( What happened was that the machine would die out of memory. Later I saw on Alan Cox's site that kernel 2.2.12 was out and it fixed a TCP memory leak. I upgraded and that was it. ;)
The problem was not even closely related to mailman. It *thought* it was because I had just installed mailman on that week. :)
Cheers,
fc
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"FC" == Fabricio Chalub <chalub@actech.com.br> writes:
FC> Actually no. :( What happened was that the machine would die
FC> out of memory. Later I saw on Alan Cox's site that kernel
FC> 2.2.12 was out and it fixed a TCP memory leak. I upgraded and
FC> that was it. ;)
FC> The problem was not even closely related to mailman. It
FC> *thought* it was because I had just installed mailman on that
FC> week. :)
Okay, thanks. -Barry
![](https://secure.gravatar.com/avatar/c8e36f7bd676686e9e9577b1a1a5b771.jpg?s=120&d=mm&r=g)
Oh, I'm sorry, it wasnt a TCP memory leak. It was just a memory leak :))
On:
http://www.linux.org.uk/VERSION/relnotes.2212.html
"Linux 2.2.12 is the latest update to the Linux kernel tree. It fixes the memory leak bug in the 2.2.11 kernel. In addition it updates various drivers and the platform specific support. The out of the box tree supports the Alpha, PPC, Sparc and X86 platforms. MIPS is mostly merged but you should obtain the platform specific tree. It is hoped MIPS and PowerPC will soon be fully merged. ARM and M680x0 users should get their platform specific tree."
fc
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"FC" == Fabricio Chalub <chalub@actech.com.br> writes:
FC> I send a e-mail a while ago saying mailman was causing a huge
FC> load on my server. That's not correct. I found out that it
FC> was a problem in the 2.2.11 version of the linux kernel. I'm
FC> with 2.2.12 now and its ok.
Can you provide any more information? Do you know what specifically about the 2.2.11 kernel was causing the problem?
I've been closely monitoring python.org after installing Jeremy Hylton's pipermail performance improvements and I've been extremely happy. Python.org can now easily keep up with the traffic. Not to say there aren't more improvements possible, but the 80/20 rule definitely comes into play. The changes may be good enough to warrant a 1.1 release even before the I18N stuff gets merged in.
-Barry
![](https://secure.gravatar.com/avatar/c8e36f7bd676686e9e9577b1a1a5b771.jpg?s=120&d=mm&r=g)
Actually no. :( What happened was that the machine would die out of memory. Later I saw on Alan Cox's site that kernel 2.2.12 was out and it fixed a TCP memory leak. I upgraded and that was it. ;)
The problem was not even closely related to mailman. It *thought* it was because I had just installed mailman on that week. :)
Cheers,
fc
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"FC" == Fabricio Chalub <chalub@actech.com.br> writes:
FC> Actually no. :( What happened was that the machine would die
FC> out of memory. Later I saw on Alan Cox's site that kernel
FC> 2.2.12 was out and it fixed a TCP memory leak. I upgraded and
FC> that was it. ;)
FC> The problem was not even closely related to mailman. It
FC> *thought* it was because I had just installed mailman on that
FC> week. :)
Okay, thanks. -Barry
![](https://secure.gravatar.com/avatar/c8e36f7bd676686e9e9577b1a1a5b771.jpg?s=120&d=mm&r=g)
Oh, I'm sorry, it wasnt a TCP memory leak. It was just a memory leak :))
On:
http://www.linux.org.uk/VERSION/relnotes.2212.html
"Linux 2.2.12 is the latest update to the Linux kernel tree. It fixes the memory leak bug in the 2.2.11 kernel. In addition it updates various drivers and the platform specific support. The out of the box tree supports the Alpha, PPC, Sparc and X86 platforms. MIPS is mostly merged but you should obtain the platform specific tree. It is hoped MIPS and PowerPC will soon be fully merged. ARM and M680x0 users should get their platform specific tree."
fc
participants (2)
-
Barry A. Warsaw
-
Fabricio Chalub