The KACE agent patch detection engine, under certain workflows, can be highly disruptive: pegging disk I/O, pegging CPU, RAM usage >1GB, and causing USB HID (keyboard) events to be dropped.
Currently the engine runs full bore, as fast as possible.
A beneficial feature would be customizable resource consumption for the detection engine to facilitate enhanced end-user experience for use cases when detection/deployment must occur during business hours.