RE: To Commit or NOT to Commit

Steve Adams clarified the cost of frequent commits earlier....

"Every commit waits for a log write and 3 scheduling latencies. There may be good reasons for coding procedures to commit intermittently,but you should keep those commits as infrequent as possible. Regards,
Steve Adams
http://www.ixora.com.au/"

Each commit will (1)release all row and table locks, (2) erase any savepoints marked since last commit, (3)and the log write.

Imagine the cost of a million commits rather than 2000 commits during an imp procedure would enlighten anybody.

-----Original Message-----
From: guy ruth hammond [mailto:grh_at_agency.com] Sent: Tuesday, May 23, 2000 3:54 AM
To: Multiple recipients of list ORACLE-L Subject: Re: To Commit or NOT to Commit

Atish Prasad Das wrote:
>
> frequent commits are always good...

Yes and no. I remember one developer who was importing million-line text files, and committing after each row. And I remember the look of shock on his face when I modified his program to commit every 500 rows and improved its performance by an order of magnitude... and we could probably have achieved even greater performance by proper tuning and optimization. :0)

g

-- 
guy ruth hammond <grh_at_agency.com> | Happiness is a loaded weapon, and
Technology Analysis & Consulting  |   a short cut is better by far.
07879607148 http://www.agency.com |     -- The Sisters of Mercy


-- 
Author: guy ruth hammond
  INET: grh_at_agency.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).