Edit replica settings

As a TeamForge site administrator, you can configure replica settings for the polling frequency of the master, and repository initialization and synchronization events.

Replication events, such as creating new repositories and synching commits, are stored in a queue on the TeamForge application server. The replica server polls the TeamForge application server for new events and then processes those events on the replica server.

These events are divided into two separate pools:

New repository initializations - this includes creating the repository and performing the initial synchronization of the content.
All other events

When existing repositories are selected for replication, this can take a long time. It could take many hours or even days to fully replicate an entire repository across a WAN. These big events are processed in their own thread pool, so that other repositories which are already synchronized don't have to wait in line for them to finish.

For each pool, you can define how many simultaneous events will be processed. The higher the number, the greater the potential load on both the TeamForge replica server and the Subversion master. However, this can also decrease the wait time for a given commit to appear on the replica server.

Click Admin in the TeamForge navigation bar.
On the site administration navigation bar, click INTEGRATIONS.
On the SCM INTEGRATIONS tab, click the name of the Subversion Edge replica you want to edit.
The Edit System page for the replica appears. Here's an example:
Change the replica name or description if required.
Tip: Including the geographic location would help users select a nearby replica.
Set Command polling interval to define how frequently the replica polls the master looking for new events. The replica will process all new events when it polls. The default value for this setting is 60 seconds, but it can range from 5 to 1000000 seconds.
Set Maximum simultaneous new repository creations to a low value. New repository initializations can take a long time and generate a lot of load. So you wouldn't want to allow too many of them to run at once. This value can range from 1 to 100, but we suggest you keep it at 3 or less.
Set Maximum simultaneous repository synchronizations taking into account how many repositories you will be replicating and how many you think are likely to have commits occurring within the polling interval. This value can range from 1 to 100. You may want to set this higher than the previous field, but we suggest you keep it at 10 or less. There's no reason to enter too high a number because you are merely specifying how many synchs can run at the exact same time -- and it never runs more than one per repository.
When you've made your changes, click Save.