It’s Tip Tuesday! Today’s post comes from Natcha Roongrote, our Hub support specialist.
When using GEOVIA Hub, a number of steps can be taken to optimize performance, dependent on the environment and conditions in which the software is expected to operate. These techniques include data clean-up and data deduplication, division of the repository into stores, data load and reporting, file compression, sync optimization and the client side cache. Here are some tricks to help improve your hub performance.
Data Cleanup
Over time, Hub users can store files that are no longer relevant. Frequently users will find that they have made exact copies of files or folders that are redundant. By eliminating data that is past a certain date, and deleting temporary and redundant files, users can ensure the Hub server is not filled with unnecessary data. With diligent housekeeping, users can help reduce data load times and increase accuracy when searching for correct data.
Deduplication
If there are a significant number of duplicated files in the system, users may need to determine if files contain the same data even if the file names are different. These files should then be treated as duplicate files. Once the duplicates found, the files can be deleted to reduce the amount of stored redundant data.
Splitting the Data Repository into Stores
When using Hub, the number of files visible to any one user depends on the number of stores to which they have access. Regardless of whether or not they have downloaded the data in their stores or not, the metadata that applies to each store will be synced with the user’s machine to allow them to efficiently search, sort and filter the datasets. As a result, the smaller the datasets, the faster it is to synchronise the metadata and find relevant files.
Data Load and Reporting
Reporting on the data stored in Hub is another way to monitor and improve the performance of Hub. When the initial implementation of Hub is completed, data needs to be correctly catalogued and assigned to the correct stores. At regular intervals, it is a good idea to analyze the data to ensure files are catalogued appropriately. This will ensure that data is not “lost” in personal stores and that users are uploading files to Hub as opposed to storing it on their own machines.
File Compression
GEOVIA Hub uses a technique called differential compression to compress any data sent to and from the server. If the Hub logs confirm that Hub is spending significant time compressing data before any file synchronization takes place, then configuration settings for file compression can be edited in the Hub configuration file, named ‘Server.Host.WindowsService.exe.config’. In this file, the file types for non-compressed files can be specified. You can also specify the minimum file size that will be compressed which will prevent the compression overhead exceeding the time saved in synchronization.
Hopefully these tips help with you improve your Hub performance. If in doubt, please contact the GEOVIA Support and Services teams who can help optimize your Hub implementation.
Looking for more info on Hub? Check out Natcha’s recent post on Connecting to Hub in Surpac.Be sure to check back next Tuesday for more Tips & Tricks.
