Re: 5500 inserts/sec possible on 7.3.4?

What type of inserts are your talking about--

11M transactions, a program that does 11M reads/inserts or SQL*LOADER.

I can't address the transactions, but for the programs and in SQL*LOADER, yes, 11M is easily reachable. I have hit 4M per hour on a quad NT box with 1GB of ra and on H and V class HP Unix servers. BUt these were test programs. In production, I have one app that is doing about 1M per hour (4 tables of about 1/2M each. The problem you might hit is with the indexes. Once you have the 151M rows, you will have a better knowledge.

In article <36792DBD.23C1F614_at_iname.com>,   Billy Newport <billynewport_at_iname.com> wrote:
> I'm currently trying to build a server which can store 5500 rows per
> second. Its purpose is solely to check for duplicate records. All the
> data in the table is part of the primary key. The table will be
> partitioned 14 ways based on the most significant field DAYNUM
>
> CREATE TABLE UTXDATA (
> DAYNUM CHAR(1) NOT NULL ,
> STARTTIME NUMBER(6) NOT NULL,
> DURATION NUMBER(6) NOT NULL,
> PRODUCTCODE CHAR(2) NOT NULL,
> DETAILS CHAR(30) NOT NULL,
> PRIMARY KEY (DAYNUM, STARTTIME, DETAILS, DURATION, PRODUCTCODE))
> ORGANIZATION INDEX
>
> Basically, I need to insert 11,000,000 records per day and keep them
> online for 14 days. I drop the "oldest" partition each day and then
> store the days records in the now empty parition. The system continues
> for-ever round robin like this. If the insert fails then I know there is
> a duplicate and tag the data for reporting later, this happens 0.01% of
> the time. I'm using an 8 CPU RS6000 with 2GB RAM and 8 9GB SSA disks for
> my test system (its what was available quickly!). There will be another
> machine heavily threaded inserting the rows to the database.
>
> I'm planning on stripping the disks for storing the table data. I think
> the biggest problems will be the redo and rollback writing. I wondering
> how best to split the 8 disks (these disks are used only for data, the
> OS and oracle are located on another disk) up in terms of strip/not
> strip, how large the strips are for redo, rollback or data etc. The
> usual.
>
> Does anyone have any suggestions for tuning such a beast or for instance
> parameters. The only thing the box will be doing is this. Think of it as
> the ultimate insert operation box.
>
> Any help apprec.
> Billy
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Dec 18 1998 - 13:59:51 CST