![]() |
|
SureSync requires a database to store configuration information. The following formats are supported:
This is the program which allows the user to configure SureSync jobs. Generally, this program is only launched when checking on the status of the jobs, making a configuration change or adding more jobs. The SureSync desktop application is not left running all the time. It will consume somewhere between 20MB-50MB of memory when running in most environments. The more jobs which need to be displayed, the higher the memory usage.
This service provides the functionality of the SPIAgent Add-on and will always be running on the SureSync machine always and on the remote machines involved in the synchronization when using SPIAgent functionality. This process consumes minimal memory and CPU time. Generally less than 1% CPU time when running a normal job. Processing a delta, using compressing or using encryption can increase this for small periods of time during processing to 1-5%. The process normally consumes less than 3MB of memory. This can increase during the processing of deltas on a large file to as much as 100MB and then go back down to normal usage.
This process is the Scheduler service which looks for work to do and launches Schedules and Monitors at the appropriate times. This consumes less than 10MB of memory in most installations and consumes next to nothing in terms of CPU time.
A SyncFiles.exe is generated for each running manually launched Relation, Schedule or Real-Time Monitor. For example, if you have 3 Real-Time Monitors running and one Schedule currently executing, you will have 4 SyncFiles.exe processes running on the machine. When a Relation or Schedule completes, the SyncFiles.exe goes away until the next execution time. With a Real-Time Monitor, the SyncFiles.exe is always running unless the Monitor is placed on hold. In general, this process will consume between 15MB and 30MB per process. However, this will vary depending on the environment and what the specific process is doing at any one time. CPU and memory usage will temporarily increase during things such as a directory scan. The more threads you have running for a particular job, the more resources the SyncFiles.exe process will consume. If you’re processing huge directory structures, your memory usage will be higher compared to an environment with small structures. It is recommended to do some testing in the specific environment to determine a more accurate number. However, if you figure 30MB for each running synchronization job you’re probably in the ballpark for more environments.