Large static read only table performace impact
Hi,
Our company is thinking to put a large table into the production system. This table
- Contains millions of rows.
- Have thousands of users.
- May have hundreds of concurrent accesses.
- The users can only access this table through one particular application
- The application guarantees the access to the table through primary key.
So no table scan.
- There is no update or insert to this table. It is a static read only table.
- So there is no worry about hot blocks or index split contention.
- Assuming database version is 10.2.0.5
Probably I may need larger buffer cache in SGA to accommodate the large volume of reads?
Our company is thinking to put a large table into the production system. This table
- Contains millions of rows.
- Have thousands of users.
- May have hundreds of concurrent accesses.
- The users can only access this table through one particular application
- The application guarantees the access to the table through primary key.
So no table scan.
- There is no update or insert to this table. It is a static read only table.
- So there is no worry about hot blocks or index split contention.
- Assuming database version is 10.2.0.5
Probably I may need larger buffer cache in SGA to accommodate the large volume of reads?
0