Person Match \/ Pre-Processed Footage
\nAmong those two modes, the one with the fastest search speed is Pre-Processed Footage. This function classifies objects in advance (pre-processing), stores them in a separate database server (MariaDB), and searches through PM service if necessary. It has the advantage of faster search speed compared to Recorded Footage mode.
\nAlso, when PM service is running, it is good because the search session resource is not consumed because it connects to MariaDB instead of directly connecting to the recorder. Devices like NVR only have two search sessions, so if there are many users who use ISS playback at the same time, the search session of NVR full may occur and PM search of NVR may not be possible.<\/p>\n
In summary, the advantages of Pre-Processed Footage are:
\n– Fast search speed
\n– It is suitable for the system environment that has the restriction of search session such as NVR or TVR.<\/p>\n
However, this service also has its weakness.
\n– Increased cost: IDLA Server and MariaDB storage capacity are required because pre-processing is required using IDLA and DB is stored by building MariaDB. That incurs additional costs.
\n+ However, if you are a user who already uses IDLA, there is no cost issue. (You only need to add as much storage capacity as MariaDB)<\/p>\n
– Restriction that only cameras analyzed through IDLA can be used:
\n+ Data analyzed in advance through IDLA are stored in MariaDB, and this data is used by PM service, so there is a limitation that only cameras analyzed through IDLA can be used. \/ There is a restriction that other cameras cannot use PM service.
\n+ But you have to think about this, there are some cameras all people must pass through. For example, building entrances, checkout counters.<\/p>\n
Therefore, it is necessary to recognize the pros and cons of the function and introduce the most appropriate service to the customer.<\/p>","protected":false},"excerpt":{"rendered":"