Deploying a small or medium StarTeam configuration

0 Likes
over 8 years ago

Small to Medium StarTeam Configurations

 

A small to medium StarTeam configuration typically consists of no more than 100 concurrent users.  For environments of this size all of the Star Team components can be implemented on a single Server machine.

 

 

Diagram:  Basic and MPX StarTeam Components deployed on shared server.

 

You should use a single machine for all StarTeam server components only when the total number of concurrent users for all configurations does not exceed 100. Even though a single configuration can support more than 100 users, each configuration has a certain amount of overhead. Consequently, we recommend that when the total peak concurrent user count reaches 100, it’s time to move at least one configuration to its own machine.

 

With a single machine, all StarTeam Server processes, the root Message Broker, root Cache Agents, and the Database Server process execute on one machine. Here are some rules of thumb for this layout:

 

• Start with 1 CPU and 1 GB of memory for the database server process. 

• Add 1 CPU and 1 GB of memory per StarTeam configuration. 

• If you use locally-attached disk for each StarTeam configuration’s vault and database partitions, use separate, fast drives to improve concurrency. Also, the disks should be mirrored to prevent a single point of failure.

 • If you deploy MPX, all StarTeam configurations can share a single root MPX Message Broker. Though not shown, one or more remote Message Brokers may be connected to the root Message Broker.

 • If you deploy Cache Agents, each configuration needs its own root Cache Agent, which can share the root Message Broker. Though not shown, one or more remote Cache Agents may be connected to each root Cache Agent.

 • Be sure to configure each StarTeam Server, Message Broker, and root Cache Agent process to accept TCP/IP connections on a different port.

 Using these guidelines, you can deploy three to four small StarTeam configurations on one machine— again, only if the total number of concurrent users doesn’t peak above 100 or so. Otherwise, the various processes could begin to compete for resources (CPU, memory, disk I/O, and/or network bandwidth), adversely effecting responsiveness. Also, if you start out with the single-server configuration, don’t forget to plan on moving components to their own machines when demand grows over time.

 Further configuration recommendations can be advised by contacting StarTeam Support.

Labels:

How To-Best Practice
Comment List
Anonymous
Related Discussions
Recommended