Re: CPU
From: belvilad (andy_belville_at_emcare.com)
Date: 09/22/05
- Next message: Oraboy: "Re: CPU"
- Previous message: belvilad: "Re: Getting password expiration date"
- In reply to: Oraboy: "Re: CPU"
- Next in thread: Oraboy: "Re: CPU"
- Reply: Oraboy: "Re: CPU"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 22 Sep 2005 09:22:29 -0700
Let's see...
Again, we too have seen differing results from Oracle between
development and production, but often this boils down to the data in
the db and the different queries (and volume quite frankly) between the
environments.
Personally, I'd be looking at data that is a bit more detailed here
before jumping to any conclusions. For example, sar -Mu will tell you
some of the same information your seeing with Vmstat, but will break it
out based on CPU and tell you how much waiting on io you're doing (your
cpu loads could be caused by something else like a disk bottleneck of
filesystem misconfiguration).
Ultimately high queue lengths mean that your system has quite a bit of
processing backlock waiting on the CPU's and ultimitely might manafest
itself into digruntled users.
The cause of that backlog is what your trying to determine. Is it a
misconfigured oracle environment? Does the CPU load go down at night
when the users log off (maybe it's not oracle, but a Unix system
problem). Is your NIC card overloaded on the production box, etc.
Applications like top, Glance, perfux, etc might help you to dive a bit
deaper into what exactly is causing the backlog.
- Next message: Oraboy: "Re: CPU"
- Previous message: belvilad: "Re: Getting password expiration date"
- In reply to: Oraboy: "Re: CPU"
- Next in thread: Oraboy: "Re: CPU"
- Reply: Oraboy: "Re: CPU"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
