The fastest scanner claim is not meaningful unless tools doing the same job are measured under the same conditions. Depth of discovery and accuracy should be compared as well as the number of devices.
Basic approach
The total time of a tool that only pings and a tool that collects identity and service information is not directly comparable. Pre-full cache, timeout, parallelism and network conditions affect the result. Writing the scope of the test makes the comparison repeatable.
Application steps
- Use the same target range and common protocol scope.
- Separate cold and hot cache conditions and do multiple iterations.
- Report time, number of known devices found, misclassification, processor and memory usage.
Practical example
If one tool finds 20 real devices in 2 seconds and the other finds 30 real devices in 4 seconds, considering the first one as superior based on the time alone is an underestimation. You also can't measure missed devices without the expected 30-device checklist.
Interpret the result correctly
Synthetic testing and loopback testing are not substitutes for a real device fleet. Express results limited to the tested environment. Share numbers with hardware, version and method used, rather than unquantified world leadership claims.
Source and follow-up reading
Protocol or command details: RFC 2330. The steps and example scenario are IPScans editorial narrative.