In order to perform an adequate server sizing, you should first know the number of cameras, the specific plugin and for each camera the number of sensors that you will probably insert. Furthermore, you should also take into consideration if you want/need to store images as well about the event. Indeed, the number of images and the timespan during which you wish to store them are crucial to perform a proper sizing.
With these context, the hardware specifications for event management can be computed in the spreadsheet that can be downloaded at the following LINK.
In the file you will be guided through the following steps:
The first step consists in typing the number of sensors for each plugin that you will use. The corresponding cell will be enabled for computation and it will change the color, from red to green, confirming the successful choice of the plugin.
According to the type of sensor chosen in the previous step, the appropriate field will be enabled, thus allowing you to enter the average number of events (each hour) that you plan to manage.
N.B.: Storage sizing is strongly influenced by this data. The higher is the number of expected events, the higher will be of course the amount of memory you will need in your project.
In this section, bearing in mind that the choice applies to all the plugins that communicate with the dashboard, the following parameters need to be be entered:
N.B.: As you can see from the image, the spreadsheet divides the plugins according to the sensor type. The difference between the two types of sensors lies in the mechanism of event detection and sending. As a matter of fact, an aperiodic plugin as AI-PEOPLE, detects and sends the event only when a person crosses the counting sensor; on the other hand, a periodic plugin as AI-CROWD, counts instead the number of people in the area and sends notifications each 60 seconds.
In this step you will visualize the hardware requirements to manage the events in the desired timespan. In this step you will only get a partial visualization of data, divided according to the two sensors types.
N.B.: In case you haven’t chosen any type of sensor, the section will remain blocked
Finally, you can visualize the hardware requirements needed to store and process the events according to the specific needs. The result is computed as a sum of the hardware required for two types of sensors, plus the basic resources needed for the proper functioning of the dashboard.