Re: benchmark to disprove myths

Ed Stevens wrote:

> My partner and I are still disagreeing on two prime issues covered in this
> summer's famous "Oracle Myths" discussion. We're also disagreeing on the value
> of separating redo logs, archive log files, and other data. All of this has to
> do with placement of different files on available disk arrays and how to best
> configure the disks in a new server.
>
> I am proposing a simple benchmark test.
>
> Have a PL/SQL to implement this pseudo-code:
>
> Create table my_test
> (empno number,
> last_name char(10)
> first_name char(10)
> street char(10)
> city char(10)
> state char(2)
> zip char(5)
>
>
> for x = 1 to 100,000
> insert row using x as the empno value
> commit
> next x
>
> for x = 1 to 100,000
> update my_test
> set last_name = 'xxxxxx',
> first_name = 'xxxxx'
> street = 'xxxxxx'
> city = 'xxxxxxx'
> state = 'xx'
> zip = 'xxxxx'
> where empno = x
> commit
> next x
>
> what I propose is running this with various placements of data, index, redo,
> rbs, and archive logs. What I hope to demonstrate is the value (or lack
> thereof) of
>
> 1 - separating index and data
> 2 - giving redo its own raid set
> 3 - giving archive logs their own set
>
> Does this sound like a resonable means of proving/disproving long held
> assumptions and the assurances of our hardware guys who insist that drives are
> now so fast that we can ignore these kinds of considerations?
>
> --
> Ed Stevens
> (Opinions expressed do not necessarily represent those of my employer.)

The basics look good and I'll be interested in the results. But I would suggest a minimum of 10,000,000 rows and including a VARCHAR2(1000) column, fully loaded, so that it is clear to Oracle that it will be faster to read an index than read the table.

Daniel Morgan Received on Thu Dec 05 2002 - 10:55:05 CST