public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Hunter <sean@dev.sportingbet.com>
To: matthew <matthew@mattshouse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test10 Sluggish After Load
Date: Wed, 1 Nov 2000 15:26:29 +0000	[thread overview]
Message-ID: <20001101152629.B31394@bart.dev.sportingbet.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011010845210.6574-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.21.0011010845210.6574-100000@localhost.localdomain>; from matthew@mattshouse.com on Wed, Nov 01, 2000 at 09:00:29AM -0600

Pardon my speculations (if I am wrong), but isn't this an oracle question?  

Isn't oracle killing the server by trying to clean up 1800 connections all at
once?  When they're all connected, most of the work is done by one or two
oracle processes, but when you kill your ddos thing, all of the oracle
listeners (of which there is one per connection), steam in and try to clean up.

I thought oracle had an internal connection limit (on our servers it is set to
440 connections), anyways.

Sean

On Wed, Nov 01, 2000 at 09:00:29AM -0600, matthew wrote:
> 
> 
> I'm evaluating my company's needs for a new database server which means
> that I get to beat the hell out of the contenders.  I'm a long time Linux
> user, and the founder of the Orasoft Project (Oracle Apps for
> Linux).  There, I'm no Linux spring chicken. :-)
> 
> I wrote stress testing apps that simulates extreme database load.  I ran
> it against 2.4.0-test9 and locked it up solid on two occasions.  I grabbed
> 2.0.4-test10 and reran.
> 
> I was impressed.  The distributed stress tester (DDOS) created 1800 Oracle
> connections, and then proceeded to bang on the server by selecting random
> connections and executing SELECT statements.
> 
> Load average got to 5.48.
> Memory was depleted, and 200M remained of the 800M swap.
> 
> After being pleased by the results, I killed the stress tester.  That's
> when things went to hell.  After the stresser was dead the server's load
> average spiked to 795!  I still had a remote console open so I tried to
> run some things.  The pstools would hang for about 20 minutes before
> spitting out data.  Just hitting ENTER in my ssh session would take 10
> minutes to register with the server.
> 
> The machine shouldn't be under any kind of load right now, yet it's acting
> as though it's getting killed.
> 
> I've left it in this condition.  It's still accepting SSH connections,
> albeit very slowly.  If anyone want to take a look I'll create an account
> and allow SSH.  I'd prefer it to be someone that I know, or someone with
> an @redhat||suse||etc e-mail address.
> 
> Here's the hardware:
> 2x 500mhz PIII
> 256M RAM
> 100% SCSI
> HP Kayak
> Kernel 2.4.0-test10
> 
> Here's some stats just before I killed the stress tester:
> 
> [root@oserv02 /root]# pstree 
> init-+-atd
>      |-crond
>      |-gpm
>      |-kflushd
>      |-klogd
>      |-kreclaimd
>      |-kswapd
>      |-kupdate
>      |-6*[mingetty]
>      |-1803*[oracle]
>      |-portmap
>      |-sendmail
>      |-sshd---sshd---bash---pstree
>      |-syslogd
>      |-tnslsnr
>      |-wu.ftpd
>      `-xfs
> 
> [root@oserv02 /root]# w
>   9:40pm  up 26 min,  1 user,  load average: 4.40, 5.48, 4.10
> USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU  WHAT
> root     pts/1    matthome.godfrey  9:29pm  1:38   5.94s  4.57s  w
> 
> 
> [root@oserv02 /root]# cat /proc/meminfo 
>         total:    used:    free:  shared: buffers:  cached:
> Mem:  261881856 259772416  2109440        0   212992 24477696
> Swap: 814178304 524578816 289599488
> MemTotal:       255744 kB
> MemFree:          2060 kB
> MemShared:           0 kB
> Buffers:           208 kB
> Cached:          23904 kB
> Active:          15268 kB
> Inact_dirty:       180 kB
> Inact_clean:      8664 kB
> Inact_target:    12036 kB
> HighTotal:           0 kB
> HighFree:            0 kB
> LowTotal:       255744 kB
> LowFree:          2060 kB
> SwapTotal:      795096 kB
> SwapFree:       282812 kB
> 
> I'm not on the list, so direct your reply to matthew@mattshouse.com.
> 
> Matthew
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-01 15:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-01 15:00 2.4.0-test10 Sluggish After Load matthew
2000-11-01 15:26 ` Sean Hunter [this message]
2000-11-01 17:10   ` matthew
2000-11-01 17:13     ` Sean Hunter
2000-11-01 17:29       ` Rik van Riel
2000-11-02 11:09   ` Alessandro Suardi
  -- strict thread matches above, loose matches on Subject: below --
2000-11-01 15:44 Jonathan George
2000-11-01 16:05 ` Rik van Riel
2000-11-03 12:54   ` Christoph Rohland
2000-11-04 13:05     ` Rik van Riel
2000-11-04 20:04       ` Christoph Rohland
2000-11-05 13:36         ` Rik van Riel
2000-11-05 18:49           ` Christoph Rohland
2000-11-01 16:18 Jonathan George
2000-11-01 16:56 ` Rik van Riel
2000-11-02  8:48   ` Christoph Rohland
2000-11-02 13:52     ` Rik van Riel
2000-11-02 16:22       ` matthew
2000-11-04  1:31         ` Peter Samuelson
2000-11-01 16:59 ` matthew
2000-11-01 17:11   ` Rik van Riel

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=20001101152629.B31394@bart.dev.sportingbet.com \
    --to=sean@dev.sportingbet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@mattshouse.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