Models Performance
Models are complex, active server resources that may have a significant performance impact. The "engine" of a model is its bindings and rules.
Model's performance impact is a multiplication of the following:
-
Number of the model's instances. An absolute model has just one instance, while a new instance of a relative model is created for every resource it's attached to. Thus, a single relative model can have thousands of instances.
-
Number of the model's bindings.
-
Frequency of model 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.
-
Frequency of model variable reads/writes, model function calls, and model event generation performed by other active system components (such as alerts, trackers or widgets).
-
Complexity and impact of binding expressions and model rule 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 Java code implementing the model's functions.
Model's concurrency settings can be adjusted if it isn't capable of processing all its bindings in time.
Was this page helpful?