[BENCHMARK] 2.5.60-mm2+anticipatory results with Oracle db load

[lkml@dm.cobite.com]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2493 bytes --]


Andrew and list,

I've been tracking various kernels with my 'production load'.  The 
load and the platform are described below.  

As stated in the subject line, this is 2.5.60 + mm2 + all three 
anticipatory IO scheduler patches from experimental/

In case anyone is comparing these to prior results, be warned, I've
changed CPUs, changed Oracle tuning, and of course, changed kernels.  
Only the relevant kernels for comparison are included below (i.e. these 
runs are on the same HW platform with same Oracle config).

If you would like to see other tests, let me know.  

As per a prior request, I've attached 'vmstat 10' output during the run 
(and a bit after).  It's compressed.  If this vmstat is useless, let me 
know, I feel a bit bad spamming the list with it.

If you'd like other profiling, let me know along with some hints on how to
use it. I tend to think this is really an I/O scheduler + user space CPU
utilization issue (not a kernel system time issue).


kernel                        minutes
----------------------------- -----------
2.5.59                        102
2.5.59-mm8                    105
2.5.60-mm2-with-anticipatory  107  <- attached vmstat.log.gz for this


Platform and configuration:
HP LH3000 U3.  Dual 1Ghz Intel Pentium III, 2GB ram.  megaraid controller
with two channels, each channel raid 5 (hardware raid) PV on 6 15k scsi
disks, one megaraid LV per PV.

Two plain disks w/pairs of partitions in raid 1 for OS (redhat 7.3), a
second pair of partitions (regular partitions with ext2) for Oracle
redo-log (in a log 'group').

Oracle version 8.1.7.4 (no aio support in this release) is accessing
datafiles on the two megaraid devices via /dev/raw stacked on top of
device-mapper (lvm2).

Workload:
The workload consists of a few different phases.
1) Indexing: multiple indexes built against a 9 million row table.  This
is mostly about sequential scans of a single table, with bursts of write
activity.  50 minutes or so.

2) Analyzing: The database scans tables and
builds statistics.  Most of the time is spent analyzing the 9 million row
table.  This is a completely cpu bound step on our underpowered system.
30 minutes.

3) Summarization: the large table is aggregated in about 100
different ways.  Records are generated for each different summarization.
This is mixed read-write load.  50 minutes or so.

-- 
/==============================\
| David Mansfield              |
| lkml@dm.cobite.com           |
\==============================/


[-- Attachment #2: Type: APPLICATION/x-gzip, Size: 13113 bytes --]