Log entries for free server cache events
FreeServerCache Begin marks the release of the old cache, and includes the following parameters:
- cacheID - The cache ID of the cache to be released by the event
- rpcCallProc - The remote procedure call value
- tid - The thread ID
- rpcid - The remote procedure call unique ID
- user - The user who triggers the event
- alloc - Process memory size
Here is an example of the log entry:
user="Full Text Indexer" tid=4992 rpcId=0, alloc=0 bytes
In some cases, a delay in the FreeServerCache call might occur when one or more threads are performing a long-running activity during the initial admin copy cache. In this case, you will see a Old Cache being held: message before the FreeServerCache Begin event as shown in the following log example:
tids= 4992
<THRD> <1 > /* Fri Nov 19 2010 11:46:06.5210 */ Cache:DecServerCount: cacheid=3 tid=4992,
threadCount now=0 tids=
This delay might degrade performance because two copies of the cache exist until the activity is completed. It will also quickly deplete memory, and the AR System server might become unresponsive.
FreeServerCache End marks the completion of the free cache event, and includes the following parameters:
- cacheID - The cache ID of the released cache
- rpcCallProc - The remote procedure call value
- tid - The thread ID
- rpcid - The remote procedure call unique id
- user - The user who triggers the event
- alloc - Process memory size
- diff - Difference in process memory size after the free cache event
Here is an example of the log entry:
user="Full Text Indexer" tid=4992 rpcId=0, alloc=0 bytes, diff=0 bytes {anchor:30337}