Its been a while since I posted. Busy with lot of things and as well some internal projects. Recently an internal project made me dig up this detail.
Sometimes people experience some kind of disk pressure on the Application Tier due to the cache filling up and then go hunting on how to set the cache settings so that they can manage the disk pressure. This is not yet (as of the time of writing this blog post) well documented in the MSDN documents for the 2010 version of the product.
One of our developers ( Remi )had passed this tip on how the TFS Application Tier cache settings are factored into the operations. Without this information some shops are left with the choice of just expanding disk space in a situation, where cache build up occurs but does not get cleared.
The following applies to the AT cache only (the real proxy is close but not identical as it does not have access to the TFS registry)
The TFS registry is the first place we look for settings:
We then validate those settings (or come up with default if not found).
<add key="applicationDatabase" value="Data Source=dbserverhere;Initial Catalog=Tfs_Configuration;Integrated Security=True;" />
<add key="WorkItemTrackingCacheRoot" value="C:\Windows\Temp\TFTemp" />
<add key="traceWriter" value="false" />
<add key="traceDirectoryName" value="%TEMP%\\TFLogFiles" />
<add key="applicationId" value="GUID here" />
<add key="dataDirectory" value="E:\" />
Caution: Be aware that doing this requires careful consideration and deliberate thought and proceed with systematic approach to tweaking the cache. I would try it on a test system OR change a few parameters (and not all at once) and iteratively reach a balanced approach.