In general, you can increase performance by binding the following objects to their own named caches:
sysindexes table and its index
Bind these two objects to the same named cache. This is the most frequently used table and its index. However, you do not have to make its named cache very large.
syslogs table
This helps reduce the contention on the buffer manager spinlocks. You should also configure a 4K memory pool in its named cache to benefit from the larger log I/O size, as defined by sp_logiosize.
tempdb database
This helps performance if many temporary or work tables are generated by your applications.
In addition to the above objects, the most frequently used tables and indexes (based on your database and application designs) are good candidates for binding to their own caches. However, if you have only one table with no index, binding that table to a named cache will not improve performance.
Having too many named caches without increasing the
total memory available to your server is generally not a good idea.
Each additional named cache reduces the amount of memory available
in the default cache.
