Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!news.he.net!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: andkovacs@yahoo.com (Andras Kovacs)
Newsgroups: comp.databases.oracle.server
Subject: Re: 30GB table: Hardware performance issue ?
Date: 3 Mar 2003 19:48:10 -0800
Organization: http://groups.google.com/
Lines: 13
Message-ID: <412ebb69.0303031948.8c7aee7@posting.google.com>
References: <412ebb69.0303031245.7c291172@posting.google.com> <b40ic5$5ul$1$8302bc10@news.demon.co.uk>
NNTP-Posting-Host: 24.203.142.9
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1046749690 24546 127.0.0.1 (4 Mar 2003 03:48:10 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 4 Mar 2003 03:48:10 GMT
Xref: newsfeed1.easynews.com comp.databases.oracle.server:178343
X-Received-Date: Mon, 03 Mar 2003 20:48:03 MST (news.easynews.com)

We are running on Oracle Entreprise Edition 8.1.7.
The index is IDX_HITORY(TimeStamp DATE, ID NUMBER) and it has 23%
selectivity.

I have maybe included a bad exemple in this post. The IN clause
doesn't cause much problem. Oracle handles it very well. Any query
that runs on this HISTORY table and uses the Index, returns 11000 rows
in about 27-33 seconds. Actually the performance of the read depends
on the number of physical read.

The CPU usage is OK 10% however the Raid 1 is running 90%.

I think that we are IO bound.