Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: commit

Re: commit

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Wed, 16 May 2001 20:19:51 +0200
Message-ID: <tg5h26g24rfb9e@beta-news.demon.nl>

"wayne" <no_at_email.please.com> wrote in message news:9dsdn2$cfg_at_dispatch.concentric.net...
> Just to add to what everyone's said: I do a LOT of batch operations, and
> through testing I have found out that if you commit after every
> insert/update vs after every 100 or more, you are running about 20%-50%
> slower. It seems to be an inverse relation (ie: follows the same pattern
 as
> y = 1/x), meaning that the difference in going from committing every 1 to
> every 100 records is many times greater than the difference in going from
> committing every 500 to every 600 records.
>
> I imagine your results will vary based on many things, but the pattern
 seems
> to lead to the same conclusion: Commiting after every DML operation is the
> absolute worst thing you could do in terms of Oracle performance.
>
>

Of course, because every individual transaction has administrative overhead.

Regards,

Sybrand Bakker, Oracle DBA Received on Wed May 16 2001 - 13:19:51 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US