public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hanna Linder <hannal@us.ibm.com>
To: Ruth Forester <lilo@us.ibm.com>, linux-kernel@vger.kernel.org
Cc: hannal@us.ibm.com
Subject: Re: Lockstats for SMP DB Workload
Date: Tue, 04 Jun 2002 18:10:25 -0700	[thread overview]
Message-ID: <55990000.1023239425@w-hlinder.des> (raw)
In-Reply-To: <200206050016.g550Gl110934@eng4.beaverton.ibm.com>

--On Tuesday, June 04, 2002 17:16:46 -0700 Ruth Forester <lilo@us.ibm.com> wrote:

> Everyone, 
> 
> I am running with the following configuration
> 
> 	2.4.19pre8aa2+dj2+ (dj2 removes global semaphore_lock spinlock)
> 	 +fast_walkA3-2_4_19-pre8_patch.
> 
> The database is set up to use raw-io, yet looking at this data, it appears that
> I am still hitting a lot of filesystem accesses, among other things.  This is an
> oltp workload, although there are some contentions (pread?) that cause the 
> cpu sys time to go to 99%, it was during this part of the "workload" that this
> snapshot of lockmeter was taken.
> 

> SPINLOCKS         HOLD            WAIT
>   UTIL  CON    MEAN(  MAX )   MEAN(  MAX )(% CPU)     TOTAL NOWAIT SPIN RJECT  NAME
> 
>         6.7%  2.5us(  25ms)   62us(  12ms)( 6.8%)   2650959 93.3%  6.6% 0.05%  *TOTAL*
> 
>   2.4%  1.0%   38us(  15ms) 3185us(  12ms)(0.13%)      6291 99.0%  1.0%    0%  kernel_flag_cacheline
>   2.3%  9.1% 6865us(  15ms) 3551us(5592us)(0.01%)        33 90.9%  9.1%    0%    do_exit+0xf4


Dave Hanson has a do_exit patch you might want to look at...

Hanna


  reply	other threads:[~2002-06-05  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  0:16 Lockstats for SMP DB Workload Ruth Forester
2002-06-05  1:10 ` Hanna Linder [this message]
2002-06-05  4:29 ` Dave Hansen

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=55990000.1023239425@w-hlinder.des \
    --to=hannal@us.ibm.com \
    --cc=lilo@us.ibm.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