Disk Usage Optimization

This chapter consists of the most important options, properties and settings for Iotellect Server disk usage optimization.

Some devices connected to Iotellect Server may produce billions of events or values updates per day, or hundreds of thousands of updates per second. Iotellect Server is capable of processing and even persistently storing such a large number of events/updates. However, some server and device account options should be fine-tuned to reach good performance figures.

• Make sure that Iotellect Server uses NoSQL database for event and configuration storage

• If magnetic (not solid-state) drives are used as a primary historical data storage, tune the NoSQL database settings to configure Commitlog Directory and Storage Directory to be located on different physical disks. To enable high performance, make sure that both commit log and primary storage are located on solid-state drives (SSD).

• Open device account properties dialog and set Settings Cache Mode advanced setting to Memory (transient cache). If the default Database (persistent cache) type is used, every device setting variable update is written to disk twice: as a persistently cached current setting value and as a historical value update event. This significantly decreases overall system performance.

• Most communication protocols designed for high performance allow devices to send asynchronous value updates that doesn't require any polling from the server side. Examples of such protocols are OPC or IEC 60870-5-104. If your device driver supports asynchronous value updates, set Synchronization Period to a larger value (e.g. one day) to prevent non-efficient polling.

Was this page helpful?

Tell us more

Send

Thank you!