RE: Tuning for High Volume of Updates of Temporary info into a Small Table ?

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Nigel Thomas  ... Have you considered retaining the rows at user logout (just mark them as deleted/logged out). That would reduce space management overheads, completely avoid index entry addition/deletion, and as a result would probably cut down on contention for index and data blocks. Of course it also means all your relevant application SQL has to filter out the rows that currently would be deleted. On login, update the row back to active (and, occasionally, insert a new row for a new user - that could be done as the user account is authorised/activated, rather than on the user's first login; removing the user's row is done only when the user account is de-activated).  

By using view application code changes can be easily avoided.

Anyway - 300 updates/sec should have a justification.

Frankly if each update means at least 1$ of revenue then your application is generating 1 mln of revenue per hour.      

Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer

--
http://www.freelists.org/webpage/oracle-l