From: Indrek Kruusa <indrek.kruusa@tuleriit.ee>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Andrew Morton <akpm@osdl.org>, netdev@oss.sgi.com
Subject: Re: Fw: Re: 2.6.12-rc2-mm2
Date: Sat, 09 Apr 2005 18:07:52 +0300 [thread overview]
Message-ID: <4257EFC8.3060804@tuleriit.ee> (raw)
In-Reply-To: <E1DK25V-0005Ye-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
>Andrew Morton <akpm@osdl.org> wrote:
>
>
>>dmesg is not clean though:
>>
>>TCP: time wait bucket table overflow
>>TCP: time wait bucket table overflow
>>TCP: time wait bucket table overflow
>>printk: 392 messages suppressed.
>>
>>What I did:
>>- "bombing" httpd with JMeter (from another computer)
>>
>>
>
>This is normal. The number of TCP connections held by
>your server in the TIME_WAIT state is exceeding
>tcp_max_tw_buckets.
>
>Check out tcp(7) on what this means and how it may or
>may not be a problem for you.
>
>
This poor Celeron machine has only 128MB RAM and tcp_max_tw_buckets were
calculated (ipv4/tcp.c) to be 16384. I have found
that increasing this number by 2048 (that's 12.5%) = 18432 is enough to
not get this overflow warning again (load average was over 90). Some
other facts:
- my current machine has 512MB RAM and calculated tcp_max_tw_buckets is
180000 (!)
- from Documentation/networking/ip-sysctl.txt: This limit exists only to
prevent simple DoS attacks
I believe that those values are somewhat miscalculated. At least by
changing calculation for machines with low memory a bit you will get
some defence against poor shouting students who had to build
load-balancing web-clusters ;)
thanks,
Indrek
next prev parent reply other threads:[~2005-04-09 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 16:36 Fw: Re: 2.6.12-rc2-mm2 Andrew Morton
2005-04-08 22:36 ` Herbert Xu
2005-04-08 23:00 ` Indrek Kruusa
2005-04-09 15:07 ` Indrek Kruusa [this message]
2005-04-09 16:14 ` Indrek Kruusa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4257EFC8.3060804@tuleriit.ee \
--to=indrek.kruusa@tuleriit.ee \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).