StarTeam Server 13.0 configuration options best practice guide

0 Likes
over 8 years ago

StarTeam Server 13.0 Configuration Options

Introduction

The starteam-server-configs.xml file contains session options for one or more server configurations. Server session options specify the core information that the Server requires to start a server configuration. StarTeam allows StarTeam Administrators to modify “starteam-server-configs.xml” to suit business needs. The Server configuration options file can be found in your StarTeam Server installation directory.   StarTeam offers a wide variety of options that can be used to optimise performance.

 

Overview of available options

Setting Name

Description

Default

Valid Range

DBMinimumConnections

Number of connections created at server start-up

10

10 – 100

DBMaximumConnections

Maximum no of db connections server is allowed to have, connections added as needed.  If max limit reached get exception with this message” Failed to acquire a database connection. Please contact an administrator to increase number of database connections”

65,535

10 – 100

MinCommandThreads

Not used

4

16

MaxCommandThreads

Number of user connection threads created at start-up

16

16-120

ItemCachePriority_File

Relative preference of file item in the server Item cache. For each type, the server calculates its dedicated share of the overall cache memory, as follows:

FileShare% = (100 * ItemCachePriority_File ) / (ItemCachePriority_File ItemCachePriority_Change ItemCachePriority_Requirement ItemCachePriority_Task ItemCachePriority_Topic ItemCachePriority_Folder ).

Any unused portion of the file share  is distributed among the other item types

100

0-100

ItemCachePriority_Folder

Similar to ItemCachePriority_File

0

0-100

ItemCachePriority_Changes

Similar to ItemCachePriority_File

100

0-100

ItemCachePriority_Topic

Similar to ItemCachePriority_File

100

0-100

ItemCachePriority_Task

Similar to ItemCachePriority_File

100

0-100

ItemCachePriority_Requirement

Similar to ItemCachePriority_File

100

0-100

ItemCacheLogRecovery

Enables logging of  item cache cleanup

0

0 or 1

ItemCacheMemoryLimit

Maximum size of item data cache in Mbytes

The max will be capped at process memory size, see setting below.

-1 ( no limit)

 

 

 

1,000 – 7,000

ItemCacheProcessMemoryLimit

Maximum allowed process memory size, used as cap for Item Data Cache size.

Win32: 1.5GB

Win32/PAE: 2.3 Gb

Wow64:                    2.8 GB

Win64:                       8.0 Gb

 

OnlinePurgeLoggingType

Logging type :Normal  =0 Verbose =1

0

0 or 1

DisableAdvancedViews

Disables creation of certain type of views

1

0 or 1

VerboseLevel

Logging type: Normal =0 Verbose =1

0

0 or 1

 

** Complete list of configuration options can be found in the “ST_Server_Help_en.pdf” **

Recommendations

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

In the following two Wiki articles we have outlined deployment guidelines:

  • Deploying-a-small-or-medium-StarTeam-configuration
  • Deploying-large-StarTeam-configurations

The below recommendations will help guide you further in optimising StarTeam Configuration.

Setting Name

Small Config

Medium Config

Large Config

DBMinimumConnections

10

10

70

DBMaximumConnections

25

50

80

MinCommandThreads

16

40

80

MaxCommandThreads

25

50

80

ItemCachePriority_File ( See below)

100

100

100

ItemCachePriority_Folder

0

0

0

ItemCachePriority_Changes  ( See below)

100

100

100

ItemCachePriority_Topic

0

0

0

ItemCachePriority_Task

25

25

25

ItemCachePriority_Requirement

0

0

0

ItemCacheLogRecovery

1

1

1

OnlinePurgeLoggingType

1

1

1

DisableAdvancedViews

1

1

1

ItemCacheMemoryLimit

( This setting depends on the physical memory. These values assume that  the machine is exclusively used for ST Server.

 

When the physical memory is not constrained  on 64bit 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 or more ( In MB) For lowerend machines use recommended values for Wow64

Win32 : 700

Win32/PAE : 600

WoW64: 1000

Win64: 60% of physical memory when physical memory is 8GB or more ( In MB) For lowerend machines use recommended values for Wow64.

           

Note:  Some of the settings above will increase StarTeam Server boot time.  DBMinimumConnections for example will have to open more threads on start up.

The recommended “CachePriority” values for all the artifacts depend on the specific use case. For customers who have CR 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.

If you have any questions on configuration options please do not hesiate to contact StarTeam support for further information.

 The downloadable document of the above informaiton is available on the link below:

http://community.microfocus.com/borland/managetrack/starteam/m/server_administration/119.aspx

Labels:

How To-Best Practice
Comment List
Anonymous
Related Discussions
Recommended