Troubleshooting Slow Replication (After Service Start)

Not all of these actions are needed. Depending on the situation, one might be more preferable than another. Changing only one of these might be enough for fixing the problem:

• Create the following registry setting in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\settings:
  step_ready_wait_time - as String Value (REG_SZ)
  The value for the setting is in seconds and defines the interval (after Tiger Bridge service starts) after which the policy work with be active - replication, reclaim space, etc.
  The default behavior is to wait for all the files on the source to be processed before starting the policy work.
• Edit the nt_work_threads_count registry setting in the same location - it configures how many worker threads are used to index the files, default is 2. A higher number of workers will speed up the indexing process. The "price" is paid in the form of increased CPU usage.
• Edit the work_threads_count registry setting in the same location - it configures how many workers are used by the policy tasks - a higher number of workers will speed up the indexing process. The "price" is paid in the form of increased CPU usage. This is not a linear increase in speed and if the number of workers is higher than the number needed to saturate the transmission channel, no speed increase will be noticed.
• Add a database_mode setting and set it to memory. The setting must be created in: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Tiger Technology\tiger-bridge\tiersvc\fstrack_settings as a String (REG_SZ). This will allow Tiger Bridge to use the memory as active storage for the files database. This will consume a substantial amount of memory - 40mil files - ~6Gb of memory.
  
  

Important: Restarting the service is required in order for any of the settings to be put in use.