Description
Despite adhering to Analytic Metadata Best Practices, users could encounter storage or performance issues. Symptoms, such as software performance issues or operating system drives that fill up, may be encountered as a result.
More devices than ever today are implementing advanced analytics to detect and classify objects within camera views or audio. Many of these analytic functions continue to emit classification data at a high rate, whether or not anything is occurring. Consider a camera configured with vehicle detection. A camera directed at a street or parking lot is likely to continue to emit metadata about each vehicle each second regardless of the fact that they may be parked, doing nothing of considerable interest to the viewer. As a result, the database receiving this metadata can grow to large size very quickly.
Product
- exacqVision Server 23.09 or higher
- exacqVision Client 23.09 or higher
Both Server and Client versions must be version 23.09 or higher to take advantage of this feature.
<br>
Solution
Maximum Days to Keep Bounding Box Metadata
Located at the bottom of the Event Linking page, just above the buttons to add and delete new event linkages, this control allows administrators to enter the maximum number of days, up to 365, to retain the bounding box data for object classification analytics.
This provides a method, beyond following metadata best practices, to aid in controlling the size of the database to improve forensic metadata search performance and limit its size. Data that reaches this threshold will be eliminated from the database.
IMPORTANT: If your drive was previously filled to capacity due to the database size, delete the eventpi.db file from the exacqVision Server directory, then restart the exacqVision Server service.
NOTE: While this constrains the size of the database, once removed these metadata points may not be used in forensic searches.
<br>
