Kbase 20398: How To set Storage Object Cache Size (-omsize)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/05/2011 |
|
Status: Verified
GOAL:
How To set Storage Object Cache Size (-omsize)
GOAL:
What is the Storage Object Cache Size (-omsize) parameter used for?
GOAL:
How to reduce users waiting on OM lock
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
The storage object cache is used to hold copies of information about the most frequently accessed objects so that they can be found quickly, with minimal overhead.
The storage object table indicates what area a table or index is in, along with other related information.
Progress allows the size to be adjustable in case it needs to be made larger at some point in the future.
-omsize is a database statup parameter.
The default value is 1024.
The minimal value of is 13, and maximum size is 65535.
The value of -omsize should accommodate objects in the database.
All tables; indices; blobs and clobs (blobs and clobs are part of OE10) are counted in this -omsize value.
A good means of determining how many objects you might need is to run the following code against the database:
select count(*) from _storageobject.
Progress Software recommends that you experiment with varying sizes to see if performance benefits are gained from larger values.