What is the problem your feature is trying to solve?
As evidenced in #885 and #1290, constrained devices have been seen to struggle as it is with Testrun's insane (nmap's terminology, not mine!) T5 timing approach.
This isn't helped by the fact the UDP scan runs concurrently, and so the device is also getting a dose of UDP port scans at the same time as it is getting a dose of TCP scans.
Describe the solution you think would solve the problem
My personal opinion is that these scans should run consecutively, not concurrently, to avoid overloading the DUT.
What is the problem your feature is trying to solve?
As evidenced in #885 and #1290, constrained devices have been seen to struggle as it is with Testrun's insane (nmap's terminology, not mine!) T5 timing approach.
This isn't helped by the fact the UDP scan runs concurrently, and so the device is also getting a dose of UDP port scans at the same time as it is getting a dose of TCP scans.
Describe the solution you think would solve the problem
My personal opinion is that these scans should run consecutively, not concurrently, to avoid overloading the DUT.