Why is my Milestone XProtect LPR server CPU usage hitting 100%?
Answered by ANPR AI·Sourced
Short answer
Check the installed LPR release, the camera workload and the recognition settings before changing codecs. High LPR server CPU usually means the server is decoding and analysing more video than it can handle, and the codec advice depends on the release: the 2024 R2 manual recommends JPEG, while the 2025 R2 manual recommends H.264, advises against JPEG and does not support H.265 for LPR.
Explanation
The LPR engine analyses decoded image frames. With H.264 the LPR server decodes the stream before recognition; with JPEG every frame arrives as a separate image, which costs far more network bandwidth. Milestone has changed which trade-off it recommends between releases, so a switch-to-JPEG fix that matched one manual is discouraged by a later one.
The reviewed manuals do not establish that H.264 or H.265 is the usual cause of high CPU. Load also rises with the number of LPR cameras on one server, the resolution and frame rate they analyse, the size of the recognition area and other work running on the same server.
Things to check
- Check which XProtect LPR release is installed and open the administrator manual for that release.
- Check the codec of each LPR camera's stream against that manual.
- Check the number of LPR cameras on the affected server.
- Check the resolution and frame rate of the LPR streams.
- Check the recognition area of each camera.
- Check other workloads running on the same server.
What to do
Follow the guide for the installed release: H.264 on 2025 R2 (not JPEG, and never H.265), or JPEG on releases whose manual recommends it, such as 2024 R2. Exclude parts of the image that do not need recognition, then measure CPU load again. Where necessary, distribute LPR cameras across servers and check recognition again afterwards.
Was this answer helpful?
Your vote decides which questions we answer next.
Cloud API
Test plate and vehicle recognition on your own images.
Send a photo or camera frame to our API and get the plate, country, make and model back as JSON. Start free, or run the same models on your own servers.
- 100 free credits every month, no card
- Plates for Saudi Arabia, Qatar, Kuwait, Bahrain and Oman
- Cloud API or on-premise deployment
Comments
Add a comment
Share what worked for you, or ask about a detail in this answer.