Commit is not to improve the performance of a single thread. It is to complete a transaction (i.e. set of SQL either is comitted or rolled back, no partial). Doing so also minimizes contention with other threads.
Bong Tumanut DBA --- "Reidy, Ron" <[EMAIL PROTECTED]> wrote: > Hmm... > > I strongly disagree. To quote from Steve Adam's website > (http://www.ixora.com.au/newsletter/2001_09.htm)... > > Over committed > > Many applications commit more frequently than necessary, and their > performance suffers as a result. In isolation a commit is not a very > expensive operation, but lots of unnecessary commits can nevertheless > cause severe performance problems. While a few extra commits may not > be noticed, the cumulative effect of thousands of extra commits is > very noticeable. Try this test. Insert 1,000 rows into a test table > -- first as a single transaction, and then committing after every > row. Your mileage may vary, but these results on an otherwise idle > system show a performance blowout of more than 100% when committing > after every row. > > Read it and test the results for yourself. Scale it to something > that fits your application's profile. I have and my conclusions > agree with Steve's findings (Oracle 8.1.7.4.0, 9.2.5.0 and 10.1 all > using dictionary managed TBS on UFS disks). > > ----------------- > Ron Reidy > Lead DBA > Array BioPharma, Inc. ===== Bong Tumanut
