The Scout Agent scales to make use of as many CPU resources as you can provide
The Scout Agent scales to make use of as many CPU resources as you can provide. For example, Scout can utilize up to 100 percent of the processing power on both low-power devices (such as a Raspberry Pi) and high-end devices (such as an Intel 32 CPU-core Xeon server), but a 64-bit processor is required regardless. High-end devices are capable of processing significantly more video frames per second.
Memory and disk requirements are relatively constant. Once Scout initializes, the process uses roughly 500MB per analysis thread (CPU core), and that memory usage will not increase. The agent records JPEG images to a disk as plates are recognized. However, Disk IO is usually not a bottleneck.
The minimum system requirements for Scout Agents are a function of:
The speed/angle of vehicles with respect to the camera (i.e., how long a legible license plate is in-frame)
The resolution of the input video
The number of camera streams analyzed by the agent
Other CPU load
The volume of vehicles (i.e., whether vehicles are seen constantly or sporadically)
Rekor maintains a list of benchmarked processors (both cloud and physical) at VGA, 720p, 1080p, and 4k resolution. Each Scout release version has its own tab in the spreadsheet. If your CPU or GPU model is on the list, write down the “System Total FPS” numbers for the resolution(s) you are interested in.
Please note that all benchmarks in our spreadsheet were conducted with Ubuntu as the operating system. If you plan to install on Windows, you should decrease the FPS values by 16-22%.
To estimate the number of cameras for a given system total FPS value, use the following per-camera rules of thumb:
- Low Speed (under 25 mph): 5-10 fps
- Medium Speed (25-45 mph): 10-15 fps
- High Speed (over 45 mph): 15-30 fps