How to Optimize Client Server
Collection-Master Client-Server is one of the most significant advances in performance, data integrity, and reliability of the product. Client-Server will leverage almost any hardware and make it “better than distributed mode”, but there are ways to improve performance.
CPU / Threads
- More Cores / Threads = Better Performance.
- VMWare license usually allows 8 cores before licensing costs increase.
- VT Recommendation:
- – 8 CPU / threads on the server. (More is better, but may be cost-prohibitive)
- VT Recommendation:
Memory
- Even though it looks like the server isn’t using memory, every last bit of available memory is dedicated to caching data.
- VT Recommendation:
- – 32 GB of Memory is the least that should be allocated.
- If the F:\CLSINC\DATA folder is larger than 32 GB, then 64 GB is appropriate.
- If the data folder is larger than 64GB, then 128 GB is appropriate.
- VT Recommendation:
Resource Monitor
Microsoft provides this tool to monitor available resources. Notice in the example that the results show that 9GB are in use and that 24GB are available. Based on that information, you might feel that 16GB would be an appropriate amount of memory for this server.
Looking more closely, you may notice that most of the “Available Memory” is allocated to Standby (Blue) with a sliver as free (Light Blue). If you see a significant amount of free memory, then the server has too much memory allocated. Standby memory acts as a cache, reducing the burden on the hard disk. You might notice as an example that pressing 1-1 to launch the Paperless File is sometimes faster than other times. When it’s fast, the Standby memory is serving the request.
Data Storage Media Strategy
In a perfect world, all storage would be the fastest flash memory storage in solid-state drives, but magnetic hard drives or cloud storage may be used for archiving data. Regardless of the storage chosen, it is important to remember that encryption at rest is an essential part of the solution.
VT Recommendation:
- Drives should be self-encrypting. Many times the storage subsystem will provide encryption.
- Use 15K RPM drives for “static information,” particularly for very large data like media.
- Moving F:\CLSINC\DATA, F:\CLSINC\HISTORY, F:\CLSINC\SHARE, and F:\CLSINC\PERM to a solid-state drive (SSD) will have a significant performance gain.
- All the folders in Secure Data will significantly benefit from an SSD drive.
| Storage Type | Description | Pro | Con | Recommended Usage |
| Solid- State Drives | Flash memory offers fast, durable, storage, but at an increased cost. Flash-based USB drives are more expensive per gigabyte of storage than magnetic or optical media, and flash-based, solid-state drives are a very cost-ineffective method of storing files. |
Fastest Storage Option |
Increased Cost |
SQL Database Primary Application Temporary Work Files |
| Magnetic Hard Drives | The cheapest form of data storage is magnetic hard drives. This option is relatively inexpensive for backing up large volumes of data. However, this method is prone to physical failure or damage, so backups need to be refreshed periodically. |
Lease Expensive Storage |
Slower Storage Option |
Archive Data Old Media Backups |
| Cloud Storage | Cloud storage uses the Internet to transfer and store files on remote servers. This has the advantage of additional security against damage since a disaster that destroys a user’s home PC is unlikely to affect servers many miles away. There are various tiers of cloud storage. The cost of this service can range significantly in price depending on the service tier selected. |
Pay only for what you use Low Upfront Cost Managed Service Off-Site Disaster Recovery |
Decreased Performance |
Archive Data Important Documents |
Collection-Master Network Diagram
