public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Strand <bstrand@switchmanagement.com>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2x Oracle slowdown from 2.2.16 to 2.4.4
Date: Wed, 11 Jul 2001 08:55:53 -0700	[thread overview]
Message-ID: <3B4C7709.50407@switchmanagement.com> (raw)
In-Reply-To: <3B4BA19C.3050706@switchmanagement.com> <20010710195821.A5730@vger.timpanogas.org>



Jeff V. Merkey wrote:

>Oracle performance is critical in requiring fast disk access.  Oracle is
>virtually self-contained with regard to the subsystems it uses -- it 
>provides most of it's own.  Oracle slowdowns are related to either 
>problems in the networking software for remote SQL operations, and 
>disk access witb regard to jobs run locally.  If it's slower for local
>SQL processing as well as remote I would suspect a problem with the 
>low level disk interface.
>
Our Oracle jobs are almost entirely local (we got rid of all network 
access for performance reasons months ago).  Before the upgrade to 
2.4.4, they were running well enough, but now (with the only change 
being the Suse upgrade from 7.0 to 7.2) they are taking twice as long. 
 I am slightly suspicious of the kernel, as much swapping is happening 
now which was not happening before on an identical workload.  I am 
trying out 2.4.6-2 (from Hubert Mantel's builds) today to see if VM 
behavior improves.

Many Thanks,
Brian Strand
CTO Switch Management



  reply	other threads:[~2001-07-11 15:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11  0:45 2x Oracle slowdown from 2.2.16 to 2.4.4 Brian Strand
2001-07-11  1:15 ` Andrea Arcangeli
2001-07-11 16:44   ` Brian Strand
2001-07-11 17:08     ` Andrea Arcangeli
2001-07-11 17:23       ` Chris Mason
2001-07-11 23:03     ` Lance Larsh
2001-07-11 23:46       ` Brian Strand
2001-07-12 15:21         ` Lance Larsh
2001-07-12 21:31           ` Hans Reiser
2001-07-12 21:51             ` Chris Mason
2001-07-13  3:00           ` Andrew Morton
2001-07-13  4:17             ` Andrew Morton
2001-07-13 15:36               ` Jeffrey W. Baker
2001-07-13 15:49                 ` Andrew Morton
2001-07-16 22:03                 ` Stephen C. Tweedie
2001-07-12  0:23       ` Chris Mason
2001-07-12 14:48         ` Lance Larsh
2001-07-12  2:30       ` Andrea Arcangeli
2001-07-12  9:26         ` [lvm-devel] " Andi Kleen
2001-07-12  9:45           ` Andrea Arcangeli
2001-07-12 17:04             ` Andreas Dilger
2001-07-12 18:18               ` Andrea Arcangeli
2001-07-12 22:55                 ` Andrea Arcangeli
2001-07-13  7:35                   ` Andreas Dilger
2001-07-13 16:07                     ` Andrea Arcangeli
2001-07-12  6:12       ` parviz dey
2001-07-11  2:58 ` Jeff V. Merkey
2001-07-11 15:55   ` Brian Strand [this message]
2001-07-11  2:59 ` Jeff V. Merkey
     [not found] <Pine.LNX.4.21.0107111530170.2342-100000@llarsh-pc3.us.oracle.com.suse.lists.linux.kernel>
2001-07-12 10:14 ` Andi Kleen
2001-07-12 14:22   ` Chris Mason
2001-07-12 16:09   ` Lance Larsh

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=3B4C7709.50407@switchmanagement.com \
    --to=bstrand@switchmanagement.com \
    --cc=jmerkey@vger.timpanogas.org \
    --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