Consider the following tips when trying to maximize the performance of your Morro Data setup:
TABLE OF CONTENTS
- Share Prioritization
- Reduce Share Exposure
- Use Replicate Shares for Scheduled Sync
- Restructure Your Data
For upsync and prefetch, shares can be configured to one of three priority levels (from highest to lowest):
- Upload after other shares
Upsync and prefetch requests from a share with a higher priority will always be executed before those from lower priority shares regardless of the order in which the requests were added to the queue.
To enable RTC:
- Go to MCM.
- Select File System, then the share.
- Go to Advanced, then RTC. Move the slider to the right to enable the feature.
The Upload menu option in the below screenshot contains the "Upload after other shares" option, which is the lowest available priority. Note that "Upload after other shares" will be disabled for shares with RTC enabled.
Reduce Share Exposure
To optimize syncing between multiple CacheDrives, consider removing access to shares from CacheDrives that do not need them. This will reduce the amount of downsyncing that must be done when file activity is performed in a share. Also, consider reserving prefetch to shares that absolutely require it. This can greatly reduce the amount of downloading done. To remove access to a share or disable prefetch:
- Go to MCM, go to Devices, and select a device.
- Go to Permissions. You will then see a list of shares. Set the permission to NO for shares that are not required to be mapped by the device. Disable prefetch by unchecking the checkbox.
This can also be done from the standpoint of the share.
- Go to MCM, the select File System, then a share.
- Go to Permissions, then select Gateway. You will then be able to set permissions or disable prefetch on the individual CacheDrives for this share.
Use Replicate Shares for Scheduled Sync
Real-time sync can be very resource heavy if there is a lot of activity, so consider using Replicate shares if scheduled sync is acceptable. Sync can then be scheduled for off-hour periods where less activity is expected or even during business hours if Internet bandwidth is sufficient. Replicate sync happens in a separate queue from normal sync shares, so large file uploads to a Replicate share will not interfere with the standard sync queue.
Restructure Your Data
If a large amount of your data is stored in a single share, it may not be handled optimally. Consider structuring your data in such a way that takes advantage of prioritization, scheduled syncing, etc. DFS can be used to simplify the view of the data for users. For example:
- Archival type data that is generally not shared across devices in real time may be suitable for a Replicate share instead of a sync share.
- Files that involve a lot of collaboration may go into a separate RTC for Design enabled share.
- Shares with data that require less than immediate sync but more than scheduled sync can have their priorities reduced.