All of lore.kernel.org
 help / color / mirror / Atom feed
From: "dada1" <dada1@cosmosbay.com>
To: "David S. Miller" <davem@redhat.com>
Cc: <lm@bitmover.com>, <albert@users.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: /proc reliability & performance
Date: Fri, 17 Oct 2003 19:24:56 +0200	[thread overview]
Message-ID: <02b901c394d3$96c662e0$890010ac@edumazet> (raw)
In-Reply-To: 20031017021040.4964309a.davem@redhat.com


From: "David S. Miller" <davem@redhat.com>
> "dada1" <dada1@cosmosbay.com> wrote:
>
> > A "cat /proc/net/tcp" takes too much time to even try it. :(
> >
> > tools like "netstat" or "lsof", (even with -n flag) are just unusable.
>
> Because they don't use the netlink TCP socket dumping
> facility which is made to handle such things much better
> than procfs ever can.

Thanks David for the hint. :) I buy it.

I found that the ss command from iproute2 package does use the 'netlink TCP
dumping' you mention (how many people on earth heard about that ?)

Instead of 15 minutes for a 'netstat -n > FILE', my server takes now 6
seconds with 'ss -n > FILE', with 200000 sockets opened.

Eric


  parent reply	other threads:[~2003-10-17 17:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  2:07 /proc reliability & performance Albert Cahalan
2003-10-17  2:34 ` Larry McVoy
2003-10-17  8:01   ` dada1
2003-10-17  9:10     ` David S. Miller
2003-10-17 14:46       ` Valdis.Kletnieks
2003-10-17 17:24       ` dada1 [this message]
2003-10-17 23:48       ` Albert Cahalan
2003-10-18  6:35       ` Willy Tarreau
2003-10-18  6:38         ` David S. Miller
2003-10-17  2:51 ` William Lee Irwin III
2003-10-17  3:24 ` Brian McGroarty
2003-10-17  4:31   ` Albert Cahalan
2003-10-17  4:56     ` William Lee Irwin III
2003-10-17  8:21     ` David Rees
2003-10-17  7:40 ` Zan Lynx
2003-10-17  7:54   ` William Lee Irwin III

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='02b901c394d3$96c662e0$890010ac@edumazet' \
    --to=dada1@cosmosbay.com \
    --cc=albert@users.sourceforge.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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 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.