Does anyone know of a good reference for understanding the effect of
pinning tables in memory.
Assume 1 Gig of RAM.
- What performance boost could I get for pinning all tables in an
address database (static, read only for the most part) (streets table -
20K rows, blocks table 300 K rows, units table 100K rows). If the cache
hit ratio indicates > 99%, is pinning any tables a waste of time
(address reads frequent, tables indexed, queries use indexes)?
- Mulitiple language support means abstracting descriptions so that a
user can view data in different languages. What effect does pinning
have on lookup tables? The point here - don't know if the cache will
always have the data. And, there isn't a large amount of data( < 20k
rows).
- If I have lots of RAM, why not keep pinning tables until I use up a
good chunk of memory? Or, pin packages/procedures that are most
commonly used (or infrequently used - because then, they wouldn't be in
the cache)???
Oracle is not clear about how to best take advantage of available RAM.
Especially, if gobs of RAM is available.
thx
Mark
Received on Thu Feb 15 2001 - 01:04:43 CST
