Recommended Configuration Options

StarTeam has a wide variety of customers ranging from small development shops with a few developers to large enterprises with tens of thousands of concurrent users. It is practically impossible to have one size fits all in terms of hardware recommendations and configuration options.

There are no hard rules about what makes a configuration small, medium, or large. However, for our purposes, we'll use these definitions based on concurrent users:

Small configuration: Supports no more than 50 concurrent users.
medium configuration: Supports no more than 100 concurrent users.
large configuration: Supports 100+ concurrent users.

This does not factor data volume or the type of users: on-line users or bulk applications. This is because, in our experience, the amount of data managed by a configuration (particularly items) tends to grow proportionally with the number of projects and views, which grows in proportion to the team size. Moreover, the ratio of on-line users to bulk applications tends to be roughly the same across organization sizes. The concurrent user count seems to be the best metric for judging configuration size for purposes of deployment planning.

So how big can a configuration get? To date, we've seen single instances with over 500 concurrent users, over 10,000 total define" users, over 4,000 views, tens of millions of items, and up to a terabyte of vault data. With continuous hardware advances and software improvements, these limits get pushed every year.

Setting Name	Small	Medium	Large
DBMinimumConnections	10	10	70
DBMaximumConnections	25	50	80
MinCommandThreads	16	40	80
MaxCommandThreads	25	50	80
ItemCachePriority_File*	100	100	100
ItemCachePriority_Folder	0	0	0
ItemCachePriority_Changes*	100	100	100
ItemCachePriority_Topic	0	0	0
ItemCachePriority_Task	25	25	25
ItemCachePriority_Requirement	0	0	0
ItemCacheLogRecovery	1	1	1
ItemCacheMemoryLimit This setting depends on the physical memory. These values assume that the machine is exclusively used for StarTeam Server. When the physical memory is not constrained on 64-bit machines , this can be set to `-1`. -1 for 64-bit translates to 8GB of IDS cache.	Win32: 300 Win32/PAE: 500 WoW64: 700 Win64: 60% of physical memory when physical memory is 8GB or more ( In MB) For lowerend machines use recommended values for Wow64.	Win32: 500 Win32/PAE: 600 WoW64: 800 Win64: 60% of physical memory when physical memory is > 8GB (in MB). For lower-end machines use recommended values for Wow64	Win32 : 700 Win32/PAE : 600 WoW64: 1000 Win64: 60% of physical memory when physical memory is > 8GB (in MB) For lower-end machines use recommended values for Wow64.

*The recommended values for CachePriority for all the artifacts depends on the specific use case. For customers who have Change-Request only configurations, it would be desirable to set ItemCachePriority_Changes to 100 and reset all the others to 0. For files-only configurations, it is recommended to set ItemCachePriority_File to 100 and reset the other options to 0.