Changes between Version 64 and Version 65 of UserGuidelines/Admin/Synchronization


Ignore:
Timestamp:
09/26/11 07:57:34 (10 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserGuidelines/Admin/Synchronization

    v64 v65  
    180180If you need to switch between jobs (e.g. for maintenance periods, low-traffic periods), you can set up multiple schedules, and disable/enable them as needed
    181181
    182 Please choose meaningful time interval and timeout settings: the more resources are to be synchronized, the longer it will take (in this regard, also note that THIS- and OTHER-policies will exchange all records in a resource, thus taking significantly longer).
    183 
    184 How many record have to be exchanged per each run depends on the average update frequency and the time internal in the job: e.g. if there are on average 100 updates per minute, and you set a 2-minute interval, then there would be 200 records to be transmitted on average. The import rate on medium-range server has been tested at on average 18 records/second, which means, the synchronization process would take around 11 seconds. To be on the safe side, choose a timeout value at least 10 times as high as that - e.g. 120 seconds in this case.
    185 
    186 Note that with NEWER-policies, the amount of network traffic arising from synchronization does not mainly depend on the frequency of synchronization, but on the record update rate at the sites. Smaller synchronization intervals would increase the traffic only slightly, but reduce the rate of conflicts and the risk of network-related problems. However, too small intervals (below the update rate of the site) may cause unnecessary network traffic with just empty transmissions.
     182'''To consider:'''
     183
     184You should choose meaningful time interval and timeout settings: the more resources are to be synchronized, the longer it will take (in this regard, also note that THIS- and OTHER-policies will always exchange all records in a resource, thus taking significantly longer).
     185
     186How many record have to be exchanged per each run depends on the average update frequency and the time internal between synchronizations: e.g. if there are on average 100 record updates per minute, and you set a 2-minute interval, then there would be 200 records on average to be transmitted every run. The import rate on a small server has been tested at on average 18 records/second, which means, the synchronization process would take around 11 seconds in this case. To be on the safe side, choose a timeout value at least 10 times as high as that - e.g. 120 seconds.
     187
     188Note that the network traffic arising from synchronization does not mainly depend on the frequency of synchronization, but on the record update rate at the sites. Smaller synchronization intervals would increase the traffic only slightly, but reduce the rate of conflicts and the risk of network-related problems. However, too small intervals (below the update rate of the site) may cause unnecessary network traffic with just empty transmissions.
    187189
    188190  - ''go back to the [#Checklist Checklist]''