QueryCacheMaxMemKB
The maximum size, in KB, to use for a per-query cache to speed up security checks in cases where the system contains many non-unique ACLs (for example, where security is inherited from a top level folder). If the same ACL has already been evaluated during the query, Content does not need to call the security DLL again. Content wipes the cache after each query.
Set QueryCacheMaxMemKB
to -1 for an unlimited cache size, or set it to 0 to disable the cache.
NOTE: The limit applies only to a single query, so if you have simultaneous queries, each one can use this amount of memory for the cache. The actual memory usage is proportional to the size of the unique ACLs that Content evaluates.
If the cache is too small, Content does the full check.
NOTE: This change is only relevant to security models where the DLL load is required for evaluation (for example, there is no need to use this parameter with NT_V4 security).
Type: | Long |
Default: | 0 (no cache) |
Required: | No |
Configuration Section: | Security |
Example: | QueryCacheMaxMemKB=1024
|
See Also: |