From: Simon Kirby <sim@netnation.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: Really slow netstat and /proc/net/tcp in 2.4
Date: Fri, 12 Oct 2001 15:10:33 -0700 [thread overview]
Message-ID: <20011012151033.B12311@netnation.com> (raw)
In-Reply-To: <20011011114736.A13722@netnation.com> <200110111930.XAA28404@ms2.inr.ac.ru> <20011011125538.C10868@netnation.com> <k2sncok4z2.fsf@zero.aec.at>
In-Reply-To: <k2sncok4z2.fsf@zero.aec.at>; from andi@firstfloor.org on Fri, Oct 12, 2001 at 09:56:01PM +0200
On Fri, Oct 12, 2001 at 09:56:01PM +0200, Andi Kleen wrote:
> The hash table is likely to big anyways; eating cache and not helping that
> much. If you're interested in some testing
> I can send you patches to change it by hand and collect statistics for
> average hash queue length. Then you can figure out a good size for your
> workload with some work. Longer time I think the table sizing heuristics
> are far too aggressive and need to be throttled back; but that needs more
> data from real servers.
Wouldn't just counting the lines in /proc/net/tcp be sufficient to see
how many buckets should be used in an ideal hash table distribution
scenario? (In which case the size of the hash table depends largely on a
machine's work load...)
Most of our web servers seem to have 500-1000 entries in /proc/net/tcp.
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
next prev parent reply other threads:[~2001-10-12 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 18:47 Really slow netstat and /proc/net/tcp in 2.4 Simon Kirby
2001-10-11 19:30 ` kuznet
2001-10-11 19:55 ` Simon Kirby
2001-10-12 16:44 ` kuznet
2001-10-12 19:36 ` Simon Kirby
2001-10-12 19:43 ` kuznet
2001-10-12 19:56 ` Andi Kleen
2001-10-12 22:10 ` Simon Kirby [this message]
2001-10-12 23:57 ` Andi Kleen
2001-10-13 15:07 ` Hugh Dickins
2001-10-13 16:07 ` Andi Kleen
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=20011012151033.B12311@netnation.com \
--to=sim@netnation.com \
--cc=andi@firstfloor.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.