Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Tuning for High Volume of Updates of Temporary info into a Small Table ?

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

From: Laimutis Nedzinskas <Laimutis.Nedzinskas_at_landsbanki.is>
Date: Fri, 23 Feb 2007 15:53:28 -0000
Message-ID: <5A8896FB2AFC5445A7DCFC5903CCA6B06FECDE@W03856.li01r1d.lais.net>


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
Received on Fri Feb 23 2007 - 09:53:28 CST

Original text of this message

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