RE: Caching a huge table's data in memory

Pro: It is in memory

Con: You must buy the memory. You must be sure you don't cause the box to start paging to swap ... very bad ... VERY bad.

When you live in the land of bad applications, sometimes the politics of the situation are such that you just do what you know is the equivalent of "fixing" things with duct tape -- a whole lot of duct tape -- rather than attempt to engage in a hopeless fight. Consider the case of an application that is so bad that a box with more than 50 Gb of RAM and 16 Alpha CPU's are required to handle from 6 to 10 active connections. Hey, if they want to spend the money ....

> -----Original Message-----
> What are the pros and cons of caching a table's data?

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Stephen Lee
  INET: slee_at_dollar.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).