...
Performance Optimizations
- UMS logs:
Use administrative tasks /wiki/spaces/ENLITEUMSE/pages/74449137 to automatically clean up logs (logging data, job execution data, execution data of administrative tasks, process events, asset information history) or remove old UMS log files (/rmguiserver/logs) when storage space runs out. - Firmware:
Remove unused firmware regularly. - Embedded database only:
- Optimize database regularly (UMS Administrator application, e.g. once a month)
- Check for free storage space and expand the storage size if necessary (keep at least 1 GB free at all times)
- Number of devices:
- If the device count is high (>10k) and overall performance is low, increase UMS Server and UMS Console memory. See How to Configure Java Heap Size for the UMS Server and How to Configure Java Heap Size for the UMS Console /wiki/spaces/ENLITEUMSE/pages/74449880 and /wiki/spaces/ENLITEUMSE/pages/74449164.
- Avoid too many devices (>5k) in one folder.
- Assignments:
Keep the number of assignments per device (direct and indirect) at a low level (<25). - Administrative tasks and jobs:
The more administrative tasks and jobs are created, the more heap is "eaten up", so it may be necessary to increase UMS Server memory. See How to Configure Java Heap Size for the UMS Server /wiki/spaces/ENLITEUMSE/pages/74449880. - Default directory rules:
Do not use default directory rules with the Apply rule when device boots option unless they are required. - Concurrent device requests:
If you are experiencing problems with many concurrent device requests (delays in configuration deployment or logging on to the device), open the UMS Console and use the options under UMS Administration > Global Configuration > Device Network Settings > Device Requests (thread and queue size) to control the throughput of the device requests. Contact support for recommendations.
...