Our application is taking approximately 2 seconds per camera to detect and retrieve camera information from Milestone.
On large-scale deployments with over 1,000 cameras, this results in an unacceptably long initialization time.
We would like to understand whether this delay is caused by our integration approach, the customer’s Milestone configuration, or any limitations on the Milestone side.
More details on our implementation can be found in the support case Case: MSC2057459
When you have a large-scale deployment with over 1000 cameras, fetching of configuration will take longer. You see the same behavior in the Smart Client, that the login takes longer, there is a longer wait till you see the view with cameras streaming etc. As a baseline; you cannot expect a MIP SDK based application to be faster than the Smart Client.
PS. You shouldn’t reference information in a non-public site in this public forum. Please present the data that is needed. In this case hope my answer fits even if not all information has been included.
Could you please share Milestone’s expected or benchmarked load times for camera configuration in a large-scale deployment (e.g., 1000+ cameras)? It would be helpful to understand what’s considered normal performance on your end, particularly for Smart Client and MIP SDK-based applications.
This information will help us evaluate whether our plugin’s current behavior is within reasonable bounds or if there’s room for further optimization.