The impact on CPU, memory and bandwidth
| Windows 10 and higher (64-bit) | Min. | Max. | Avg. |
| CPU | Intel i3 1.9GHz or similar | ||
| Memory Usage | 1.0% | 13.8% | 5.6% |
| RAM | 4GB | ||
| Disk space usage | 134MB | ||
| CPU usage | 0.5% | 6.2% | 5.8% |
| .NET Requirement | Version 2.0 | ||
| C++ Runtime | 2015-2019 | Redistributable (x86) | 14.28.29334 |
| MacOS Big Sur and higher | Min. | Max. | Avg. |
| CPU | Intel-based and Apple Silicon | ||
| Memory Usage | 1.0% | 13.8% | 5.6% |
| RAM | 4GB | ||
| Disk space usage | 376MB | ||
| CPU usage | 1.3% | 10.3% | 4.2% |
| C++ Runtime | 2015-2019 | Redistributable (x86) | 14.28.29334 |
| Android 8 and higher | Min. | Max. | Avg. |
| RAM | 4GB | ||
| Disk space usage | 100MB |
Windows Utilization
Below represents a performance monitoring sample from a Lenovo Thinkpad E595 with AMD® Ryzen™ 5 3500U Processor, 2.10 GHz, 4 Cores, 4 MB Cache) and 32GB of RAM.
The monitoring period lasted 240 minutes and Mobile Eye was configured to run passive tests (i.e. signal strength measurement) every 5 minutes and active tests (i.e. throughput measurement) every 10 minutes, lasting approximately 10 seconds.
The relevant processes monitored were the following:
- mobileeyeagent.exe
- java.exe
- conhost.exe
Summary of Results:
| CPU |
Peak utilization captured at time of throughput test of 11.7% Total CPU time = 0:02:47 or 1.15% |
| GPU | 0.0% |
| Memory | 0.3% utilization |
Bandwidth Utilization
7SIGNAL Mobile Eye's upload/download throughput tests are each 5 seconds long and measure the number of megabits passed over the network to the Sonar endpoint in that time.
Decrease the frequency of throughput testing by modifying the Active Test interval (default is 15 minutes) on the Configuration page, which will reduce bandwidth utilization.
A rough way to estimate traffic generation in a single direction is to multiply 4 tests/hour x number of hours active x number of testing clients x expected throughput in MBps x 5 seconds. So 4 x 24 (the busiest clients are probably running all day) x 20 x 16 (common upload throughput observed in MBps) x 5 = 153 GB in the upload direction/day.
To get the most consistent device performance measurement for throughput with the smallest impact on network bandwidth, use a local Sonar, to measure throughput across your LAN/WAN.
Throughput performance measurements to a Cloud Sonar, is the least consistent because it is limited by Internet pipe size and ISP performance.