public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Schmid <webmaster@rapidforum.com>
To: linux-kernel@vger.kernel.org
Subject: Slowdown on high-load machines with 3000 sockets
Date: Sun, 27 Feb 2005 17:53:39 +0100	[thread overview]
Message-ID: <4221FB13.6090908@rapidforum.com> (raw)

Hello.

The problem here is that starting with 3000 sockets, the syswrite locks more and more on the sockets 
although the sockets are non-blocking. This just suddenly appears at around 3000 sockets. I have 
raised min_free_kbytes to 1024000 and then it suddenly did not block anymore. I changed it down to 
16000 again and id instantly locked again. Up to 1024000 and no locking. Now it starts blocking 
again at 4000 sockets even with 1024000 min_free_kbytes, slowing everything down.... what could this 
be? Its no network-problem. I have discussed this issue with netdev-people for 2 weeks. No memory 
problem as well I suppose, its 8 gb ram with a 2/2 split...

This problem has been observed on a 2.6.10 kernel.

Please help. Thank you in advance.


Best regards,
Chris

             reply	other threads:[~2005-02-27 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 16:53 Christian Schmid [this message]
2005-02-27 17:18 ` Slowdown on high-load machines with 3000 sockets Rik van Riel
2005-02-27 21:09   ` Rik van Riel
2005-02-27 21:20     ` Christian Schmid
2005-02-27 23:32       ` Rik van Riel
2005-02-27 23:43         ` Christian Schmid
2005-02-28  0:06           ` Rik van Riel
2005-02-28  0:29             ` Christian Schmid
2005-02-28  5:13               ` Nick Piggin
2005-02-28 11:36                 ` Christian Schmid
2005-02-28 18:56                 ` Christian Schmid
2005-02-28 23:46                   ` Nick Piggin
2005-03-05 16:39                     ` Christian Schmid

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=4221FB13.6090908@rapidforum.com \
    --to=webmaster@rapidforum.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox