-
Notifications
You must be signed in to change notification settings - Fork 123
Improving performance
If used incorrectly, CmisSync might waste CPU on both the client and server. Below are a few tips that might make your CmisSync experience perfect, while avoiding to stress your ECM server.
Aegif provides professional support for CmisSync, we can help you find the strategy that fits your company the best, and implement it.
The default poll interval is 5 seconds. While this is good for tests and environments where you want to get all server changes immediately, it might prove stressful for the server. You might want to modify the setting to:
- 5 minutes (project collaboration on office files),
- 6 hours if documents just change a few times per month (sales material, documentation, records management, archives).
Many people use CmisSync to synchronize from different folders or different servers. In such cases, you might want to configure the poll interval differently for each of them. This is possible: The poll interval is configured at this level.
With a text editor like Notepad, open the C:\Users\nico\AppData\Roaming\cmissync\config.xml file (replace nico with your user name. Note: Configure Windows to show hidden files, otherwise you might not see AppData).
Spot the <folder> tag that defines the synchronized folder you want to tune. Within it, you can see a <pollinterval> tag, probably with the default value of 5000. Change the value to what you want.
The poll interval is specified in milliseconds, for instance:
- 5 minutes = 300000 milliseconds
- 6 hours = 21600000 milliseconds
If no <pollinterval> tag exist, create one like this: <pollinterval>300000</pollinterval> just above the next </folder> line.
CMIS performance can be improved by enabling CMIS compression.
Instructions for Alfresco: http://wiki.alfresco.com/wiki/CMIS#Compression
The instructions above apply for other Tomcat-based servers.
For non-Tomcat-based servers: please send us an email and we will add your instructions/tips here!
When it is implemented, ChangeLog will allow CmisSync to efficiently get the list of recent server-side changes, removing the need to crawl. Unfortunately, not all servers support ChangeLog. See how to enable CMIS' ChangeLog feature on Alfresco.
CmisSync lets the OS notify it when anything changes in a synchronized folder. This makes CmisSync very efficient in terms of local disk usage. In rare cases, you might want to disable the watcher, for instance if the server is read-only.