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: Oracle and small tables

Re: Oracle and small tables

From: Gerry Sinkiewicz <sinkiege_at_snet.net>
Date: Tue, 14 Mar 2006 22:25:55 GMT
Message-ID: <TpHRf.21607$tb3.6261@newssvr24.news.prodigy.net>

<sjaffarhussain_at_gmail.com> wrote in message news:1142233702.100182.159970_at_i40g2000cwc.googlegroups.com...
> We have an application used for online share trading and 400+
> transaction per second. There are couple of small tables, like 1 row, 8
> rows, 9 rows and 88 rows are accessed very frequently, I can say, every
> transaction, touches these tables for updates. The session who access
> these tables suddenly waits on latch free and system goes in hung
> stage. We tried to keep one row in one block, still, we face the hot
> block becuase tables are small. There an interesting paper from Poder
> presented during hotsos 2004 seminar.
>
> http://integrid.info/Poder_Small_Tables.pdf
>
>

I like the part where he says the best way to improve performance on an operation is not do it.
I think he means the system design has to be looked at with respect to real requirements and the
reasons for them.

I am surprised with the one row table in continual update mode, that you don't experience deadlocks
quite often?

The "KEEP" buffer pool is your friend. Received on Tue Mar 14 2006 - 16:25:55 CST

Original text of this message

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