How many attributes are too many attributes?

Question

The alarms on a device are coming in as an integer value and it can represent anything between 300-1100 different alarms, each with its own priority and description. 
 
 Would it be acceptable to create an $AlmObject with said number of attributes (300-1100) where each attribute represents a specific alarm? 
 Apart from taking a bit of time to open the object up in development what would the impact be during runtime when you might have 20-60 instance per area?

Michael · Accepted Answer

Marcell, There is a phsyical limit of 5000 attributes that can be created in the core Primitive of an Object. Each of these can be extended with Features such as IO, Alarms, History, etc. It might be a better model depending on your specific application needs to create a contained object model With the containment model there is no physical limit to the number of contained objects at each level of containment. THere is a limit of 10 levels of containment allowed. 
 In Runtime an Area and all it's associated objects whether singletons or contained in a hierarchy must run on a single ApplicationEngine. It is a good rule of thumb to expect an AE to hande 10,000 changes per second aggrate throughput. That should not be considered as the limit of IO refernces, defined Alarms, or Historized attributes that are configured. Rather this is the colletive rate of changes from the IO Server.

How many attributes are too many attributes?

Top Replies