Multiply that by number of cameras in use. To calculate the required disk space you need to multiply the file size by the desired fps rate, then by 60 (seconds into minutes), by another 60 (minutes into hours), then by number of hours in day that you need recording to be on for, by days, and possibly months. You can find out file size of 1 JPEG image for example by connecting a camera stream of needed image resolution to Xeoma and then use the ‘Save to File’ module. You can calculate required disk space and incoming network speed on your own: You can also read the instructions for setting up hardware decoding here. It can be used if the server is under heavy load.Ĭheck the selection of video cards recommended by our experts. Hardware acceleration is available in Xeoma. Enter these parameters:Īnd we get the following calculation of server system requirements: Recordings from all cameras are stored during 30 days, the number of simultaneously connected clients is 20. The remaining 11 cameras record according to Rare movement, using mjpeg stream of 0.36 MP for viewing, and for an archive - H.264 stream of 0.36 MP and a 512 Kbps bitrate. One more camera does not use intellectual modules, but it records continuously using mjpeg stream of 2 MP for viewing, 15 frames per second, and for the archive it uses H.264 stream of 6 MP and a 7 Mbps bitrate. All 8 cameras use mjpeg stream of 0.36 MP for viewing, H.264 stream of 3.7 MP and 5 Mbps bitrate for the archive, recording – intensive movement around the clock. Let’s consider the following example: you have 20 cameras on your site, 3 of which use the Face Recognition module, 5 cameras use the Object Detector module. Thus, system requirements are calculated more accurately and automatically summarized in the Result section. IMPORTANT: if you use intellectual modules only on several cameras, and also if the cameras use different stream parameters for viewing and recording to the archive, fill in these fields separately for each group of cameras by clicking the Add Camera button. Please note: the load on the outcoming network connection, as well as on the RAM, increases in this case. You can reduce the load on the server, if decoding is done only on Clients’ side – tick this field. The load depends on the features used and on how often (and how many) users view the cameras. If clients require remote access, tick this field and specify the maximum number of simultaneously connected clients. Intellectual modules add from 10 to 30% of the load on the server, so you should tick the modules that will be used at your site. In the Hours and Days field, specify the number of days or hours during which the archive should be stored. In the Intensive field, the choice depends on the amount of time during which the recording will be made: continuous recording (100%, 24 hours a day), intensive movement or scheduled recording (at certain hours and days of the week or only when movement is detected, which takes about 30% daily time), or rare movement (if the camera is installed in a place where people appear rarely – the recording takes 5% of the daily time). In the second line, check the Archive box if you want to save the recordings from the cameras to the archive and fill in all the fields in the same way. The Bitrate is selected in accordance with the resolution of the stream (128 Kbps – 20 Mbps). In the Resolution field, select the value in which the viewing will be made (0.03 MP-33 MP). Select the stream parameters you will use for viewing (mpeg / H.264/H.264 +/H.265 +/mjpeg). Specify the number of cameras that will be used for viewing in the Quantity field. The calculator’s first line is where you should input parameters of the cameras that will be used for viewing in real-time mode. You can read more about dual streaming here. It will help you save a lot of resources. Xeoma encourages you to use dual streaming when possible which means that you should use a stream with low resolution (for example, mjpeg) to view video recordings in real-time mode, and use a high resolution stream (for example, H.264) to save recordings to the archive. Please make sure that in your particular case the server is sufficient for the requirements you need, or consult with us. Some actions, such as search in the archive or a quick scan of the archive, can give a very heavy load to the computer. The load depends on the filters used, their settings, the number of simultaneously connected viewers and their actions. The estimates do not guarantee that a server with recommended specifications will be sufficient for the tasks assigned. The estimations you get in the calculator are approximate and may differ from real results in some cases.
0 Comments
Leave a Reply. |