Help with Tuning?

• Quoting Steve - Schow to All dated 09-19-94 ***
  > Right now, a single transaction is taking about a second.
  > Obviously if 3000 users were connected at the same time, then 3000 > seconds
  would be WAY too long to wait for a query which only returns 1
  > row!!!!
  

The math doesn't make a whole lot of sense, but neither does the 1 second transaction time. Tune the database according to your application (of course) and set it up for high concurrency. How that is accomplished may depend on your platform, but you may find that using discrete transactions will help.

> Also, it so happens that the thousands of concurrent users will be
> using the same oracle login id. So, are there any resource limits that we
> need to make sure to beef up in order to handle that many instances of a
> single user being logged in at the same time and performing concurrent
> transactions?

In a word, no. Received on Fri Sep 23 1994 - 07:18:52 CEST