There is always a way to make thing work faster, my customer has two App Tiers controlled by NLB and DB Cluster and still there is ways to improved TFS Performance.
I’ve wrote on DB Resizing and Management – Control\Reduce TFS DB Size
I demonstrate how to clear IIS Logs – Clear IIS Logs Using Task Scheduler – Although some people prefer to disable log by
Running the following command: (I don’t like it – If there is a problem disabling information will not help you solving the problem…..)
%windir%\system32\inetsrv\appcmd set config -section:system.webServer/httpLogging /dontLog:”True” /commit:apphost
Separate I/O Load By Moving Cache To a Separate Physical or Logical Drive
The last change I made to our servers made a lot of difference, as you know TFS based on IIS which means there is a cache. cache enabled so that users can download files more quickly from the cache instead of directly from the database. cache can be good but also can be bad is not managed properly.
Changing AppTier cache settings you can specify the maximum limit on the amount of storage space that the application-tier server can use for caching files. When this limit is reached, a cleanup routine makes room for newly requested files by deleting those files that have not been accessed in the longest time.
Open AppTier web.config located in :
C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services\web.config
Locate <appSettings> section and add the three new keys:
<add key=”dataDirectory” value=”E:\temp\cache” />
<add key=”PercentageBasedPolicy” value=”70″ />
<add key=”CacheDeletionPercent” value=”50″ />
PercentageBasedPolicy – specify the cache limit at 70% of available disk space before old files are removed.
CacheDeletionPercent – Amount of cache to free when removing old files based on the above policy.
dataDirectory – To specify a different cache root folder
For more informaction about changing cache – Change cache settings for an application-tier server