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

  • From: "Gints Plivna" <gints.plivna@xxxxxxxxx>
  • To: nigel_cl_thomas@xxxxxxxxx
  • Date: Fri, 23 Feb 2007 16:58:10 +0200

Reduce the number of rows in each block (increase PCT_FREE) if there is any
block contention, or row chaining

Or using minimize records_per_block clause.

We had the same problem with our home grown session pool table, we had
less users though. One of the biggest problems was that we used RAC
and hence the pinging of this particular table's and index blocks
among nodes. As we had a few parts of our application and some of them
didn't use this session table extensively we changed the connection
scheme from load balancing to mapping different nodes to different
parts of our app. It reduced the problem to minimum, but as I've said
we had at least 10 times less concurrent users.

Gints Plivna

Other related posts: