Database Tuning (MOSC)

MOSC Banner

How a Small transient table should be stored to get best performance under heavy insert/delete hit.

edited Aug 12, 2011 1:05PM in Database Tuning (MOSC) 9 commentsAnswered
Hi  Gurus,

we are having a small table almost 10k to 20k records with average row length of 200 characters. on an average this table is 50MB and index on this table is 4MB.
This table shows a lot of contention on index in our RAC environment having 3 nodes. Average hit on this table is almost 150k inserts and same number of deletes. with normal load of around 50k inserts + 50K deletes the average elapse time comes less than 20 ms and it reaches to 1500 ms when the same system is loaded little bit where number of queries triples.

I want to know what should be the best way to get a decent performance from this table. This table stores transient data and this data hardly resides for 2 to 5 seconds in this table. basically it stores lock information for few particular application operations, so that in distributed environment different application servers  can choose different jobs and check these jobs are not getting executed by other application server. 

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center