Widgets Performance
Widgets are active resources that may have significant performance impact. An "engine" of a widget is its bindings.
A widget running inside Iotellect Client may cause considerable CPU load and memory usage on Iotellect Client itself, Iotellect Server, or both.
Widget's CPU load impact is a multiplication of the following:
- Number of widget instances launched by system operators.
- Number of widget's bindings.
- Frequency of widget binding processing. It may either be explicitly specified in the binding options (for Periodic bindings) or implicitly defined by the frequency of events or state changes that trigger binding execution (for On Event bindings). See Bindings Performance for details.
- Complexity and impact of binding expressions. See expressions performance for more information.
- Impact of writing binding targets. Writing a binding target is in most cases writing a context variable or calling a context function. See variables performance and functions performance for more information.
- Impact of custom widgets scripts Java code.
Templates of the widgets are cached in the server memory to ensure quick widget startup. A large number of complex widgets can cause noticeable constant server memory usage.
Running widgets that have hundreds of complex dynamic components (such as tables, event logs, maps, graphs or dynamic vector images) may cause considerable constant client-side memory load.
Running widgets may also cause additional short memory usage bursts in case if large datasets (e.g. lots of historical events) are loaded by widget bindings or charts.
Was this page helpful?