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

Folks

Our Banking Product has an Application Login Table into which Session Connect information is INSERTED on User Login.

Approx 10,000 Concurrent Users login & hence the Table contains about 10,000 rows.

Info created by 1 session may be used by Another Database Session process. On User Logout the respective Session information Record is DELETED. An Application Load of 300 UPDATEs per second happen to the Table's different rows at random (NOT to every row) depending on the respective Application User's Transaction

NOTE - Each Update is updating a unique single row via the unique index.

What options, ideas can be considered to make the Updates faster & less CPU consuming?

Some ideas Checked already are:-

• Global Temporary Table (GTT) can NOT be used
• Benchmarked with Asynchronous COMMIT gave NO benefit
• Truncate Table periodically to reduce HWM

I will provide any Clarifications needed on this.

Thanks indeed

• CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** -- http://www.freelists.org/webpage/oracle-l