Factors that affect Genetec Mission Control™ performance - Genetec Mission Control™ 3.0.5.0

Genetec Mission Control™ Deployment Guide 3.0.5.0

Applies to
Genetec Mission Control™ 3.0.5.0
Last updated
2022-05-02
Content type
Guides > Deployment guides
Language
English (United States)
Product
Genetec Mission Control™
Version
3.0

The number of incidents Genetec Mission Control™ can handle per minute depends on the number of incident types, the complexity of the incident detection rules and automation workflows, the number of active incidents, and the rate at which events are generated in the system.

The performance metrics of your Genetec Mission Control™ are impacted by the following:
Number of events generated per second
An event can be anything as simple as an access granted event or a motion detection event.
Number of incident types configured
An incident type entity represents a situation that requires specific actions to resolve it. The incident type entity can also be used to automate the incident detection in Genetec Mission Control™ and to enforce the standard operating procedures that your security team must follow.
The configuration of your incident types also impact performance. This includes the following:
  • Configuration of incident triggers or rules for triggering an incident.
  • Complexity of the automation workflows.

    For example, a Wait for event activity in the automation workflow would impact performance.

Number of incidents triggered per minute
This refers to the number of active incidents triggered per minute.
Number of incidents active in your system
The total number of active incidents in your system at any given moment.
Other factors
  • Performance of RabbitMQ
  • Performance of your SQL Server
  • Number of servers
  • Number of clients: this includes workstations, Genetec Mission Control™ Web API clients and mobile apps.

Disk usage

  • The average size of an incident type configuration is approximately 5MB. If you have a 100 incident types, you would need 500MB of database space.
  • The average size of an active incident on disk is approximately 10 KB. If you have 3000 - 4000 incidents per day, you would need 10 GB of disk space for 1 year of retention.
  • For RabbitMQ to function optimally, a minimum of 50MB of disk space must be free.

Configuring your system architecture

Based on your requirements, you can build your system architecture using Security Center recommended server or high-end server specifications.

For example, if you have 1 to 4 operators and expect a minimum level of automation in your incident workflows, you can build your system architecture using the Security Center recommended server specifications.

If you have 5 or more operators, expect a large level of automation in your incident workflows, and have multiple servers, you can build your system architecture using the Security Center high-end server specifications.
Tip: For Security Center server metrics, refer to Security Center server requirements.

Your system performance depends on your setup. For more details on deployment architectures and their requirements, see Genetec Mission Control™ deployment options overview.