timed statistics for inserts

From: Peter Laursen <ptl_at_edbgruppen.dk>
Date: 11 Jun 1999 13:23:10 GMT
Message-ID: <01beb416$5d801d70$2c289a0a@apollo>

I getting complaints about inserts taking too long. Im not sure whether I can optimize further on these statements.

Inserting 2980 rows lasts 48 seconds, getting a sequence number for the pks adds another 48 seconds ?!
Rows are small, approx 37 bytes each.
Inserts are made using array-dml, not 2980 individual inserts.

Are these numbers normal for inserts?
If not, how could I further optimize? Caching the sequence?

tkprof details follows

Thanks
Peter

INSERT INTO SAMPLE (SAMPLETIME, VALUE, METER_RECNUM) VALUES
(:SAMPLETIME, :VALUE, :METER_RECNUM) call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ----------

Parse 1 0.00 0.00 0 0 0

0
Execute 1 21.22 48.12 66 380 35385 2980
Fetch 0 0.00 0.00 0 0 0

0
------- ------ -------- ---------- ---------- ---------- ----------

total 2 21.22 48.12 66 380 35385 2980

Misses in library cache during parse: 0 Optimizer goal: RULE
Parsing user id: 20 (ILADM)

Rows Execution Plan

-------  ---------------------------------------------------
      0  INSERT STATEMENT   GOAL: RULE

****************************************************************************

SELECT SAMPLE_SEQ.NEXTVAL
FROM
DUAL call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ----------

Parse 1 0.00 0.00 0 0 0

0
Execute 2980 0.33 0.33 0 0 0 2980
Fetch 2980 22.64 48.07 0 2980 11920 2980
------- ------ -------- ---------- ---------- ---------- ----------

total 5961 22.97 48.40 0 2980 11920 5960

Misses in library cache during parse: 0 Optimizer goal: RULE
Parsing user id: 20 (ILADM) (recursive depth: 1)

Rows Execution Plan

-------  ---------------------------------------------------
      0  SELECT STATEMENT   GOAL: RULE
      0   SEQUENCE OF 'SAMPLE_SEQ'

2980 TABLE ACCESS (FULL) OF 'DUAL'

Received on Fri Jun 11 1999 - 08:23:10 CDT