Re: Global Temporary Table performance with inserts.

People have been known to use Oracle
for multi-user systems - the fact that you cannot TIME a difference on your simple, single-user test case does not mean the
test case will perform well at high concurrency.

If (for the sake of argument) one option produces one redo entry, and the other option produces 100 redo entries, with corresponding difference in the number of redo allocation latch gets, then there is a potential concurrency issue that may be significant in a highly concurrent system.

-- 
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person
  who can answer the questions, but the
  person who can question the answers -- T. Schick Jr


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


"Daniel Morgan" <damorgan_at_x.washington.edu> wrote in message
news:1070728227.206527_at_yasure...


> Jonathan Lewis wrote:

>

 > As I recall the original post was about 100 rows and when I run


> with 100 rows I find no detectable difference.

>

> SQL> insert into t1

>    2  select * from all_objects

>    3  where rownum < 101;

>

> 100 rows created.

>

> Elapsed: 00:00:00.04

> SQL> insert into t2

>    2  select * from all_objects

>    3  where rownum < 101;

>

> 100 rows created.

>

> Elapsed: 00:00:00.04

> SQL>

>

> That is after the first run. The first time I run it I see a difference.

> All subsequent tests yield the same result.

>

> -- 

> Daniel Morgan

> http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp

> http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp

> damorgan_at_x.washington.edu

> (replace 'x' with a 'u' to reply)

>