Performance optimization

Folder structure, batch size and update frequency impact throughput from the station to the cloud. You can adjust these factors for each individual station to find the optimum setting that maximizes the usage of each sent message while minimizing the amount of time required for the data transmission.

Folder structure may already be established in your stations. But, if not, you should consider how folder structure impacts performance. Stations with a flat folder structure have shorter point IDs, which means that more of them can fit in an update message. The trade-off is that a flat folder structure means more points are in each folder. Loading and viewing these folders might take longer. Stations with a deeper folder structure (or particularly with long folder names) fit fewer points in the update message (compression will mitigate this), which may load faster when viewing a particular folder.

The cloud point device extension (double-click the Points folder) defines the point ID based on a point’s “handle.” The property in question is Use Handle For Point Id.

Batch size (also defined on the cloud point device extension) specifies how many points to include in each update. It defaults to 500. Particularly for larger stations, you can increase this number without impacting performance. Settings beyond around 5000 may not produce significant improvements due to the Sentience IoTHub’s restrictions on maximum message size. This value depends on the station’s structure, as the update includes the point ID, which depends upon the station’s folder structure.

You can also configure the update interval for each of the three update groups.