Am 17.01.2014 08:10, schrieb Pointhope: > Maximum concurrently executed NVT's per host = 4 > Maximum concurrently scanned hosts = 10 > > the CPU usage is up to 90%
what do you expect? open htop and look at the CPU usage of a single NVT process what you are doing is 10*4 = 40 NVTs at the same time > Are there any other configurable switches to improve the performance of scans? use the one above and think about how this should be faster if you overload them - limit it to one host at the same time and i bet it will be finally even faster than now because no overload > On Jan 12, 2014, at 6:32 PM, Reindl Harald wrote: > >> >> >> Am 12.01.2014 18:27, schrieb Pointhope: >>> Hi everyone, >>> >>> scanning a whole Class-C network brings openvasmd up to 99% CPU usage. >>> Forked openvassd processes are niced to 30, otherwise the system can't be >>> stopped anymore, while nothing else as openvas is running on the machine. >>> >>> Do you have similar experiences or recommendations how to proceed with >>> whole Class-C network scans? >>> >>> BTW: scanning a single host just performs as expected, but how do I add >>> multiple hosts (like 192.168.1.1, 192.168.1.2, etc)? >> >> you simply need to limit the number of hosts and tests per host at the same >> time
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
