Can the size of hashed file cache be controled?

[olgc]

Hi there,

When a hashed file "pre-load file to memory is Enabled", a warning message as the following is showed. This hashed file is very small (only three rows in it). It doesn't need 128M cache. In another case, the problem is - Unable to allocate memory - means not enough memory for the cache. SO do we have the control of cache size?


Event #:102
Timestamp:31-Mar-2004 1:55:23 PM
Event type:Info
Message:
Ret..S_HashFile.TypeDescIN: Read link private caching enabled, cache size (128MB)[size=18][/size]

[kduke]

Why not do it in a routine?

[kcbland]

When a hashed file "pre-load file to memory is Enabled", a warning message as the following is showed. This hashed file is very small (only three rows in it). It doesn't need 128M cache.

The hash file will use the minimum amount of memory necessary to cache the file. It will not EXCEED this setting. Why you get a YELLOW warning message beats me, but you did post an INFO green message.

In another case, the problem is - Unable to allocate memory - means not enough memory for the cache. SO do we have the control of cache size?

Only by limiting the data you put into the hash file to be cached. Otherwise, its a maximum cache size.

[ray.wurlod]

You have global control over the hashed file cache sizes via the Administrator client's project Tunables tab. The configuration parameter DISKCACHE can also be used.
There is a separate manual on caching hashed files (dsdskche.pdf); reading this should answer all your questions.

[kduke]

I still say 3 rows then do it in a routine.