If all or most of your visitors need this data, and you'd otherwise have to
retrieve it form a database or I file, I'd certainly cache that data. 24K
is not that much at all. I don't know what the upper limit for caching is
(if there is one), but I once read an article about backstage at
http://msdn.microsoft.com They described a method and a COM object to store
a lot of data in the application state with a Lookup table object.
Although you may not want to use the Lookup-table object as it isn't very
flexible, the links below may give you some ideas on what to cache and how.
At 07:05 PM 2/19/2001 +0800, you wrote:
>I have 24k data that is frequently used for every visitor, would it be a
>good idea to store it in an application variable? and I don't know what
>size of data is applicable for caching. Anyone has experience the maximum
>size of data for caching on the condition that it will enhance performance
>instead to be a problem? Thanks for any suggestion!
> From Ed.