A lot of this really depends on which and how many plugins you use as well as the size of your target object. You'll potentially see a lot of forked processes.
FWIW, I have a 4CPU 16GB RAM VM to scan /23 size networks (approx 500 hosts) with virtually all plugins enabled and configured. -G > As far as i am testing OpenVAS i didnt need more then 2GB. But a few day > ago linux killed openvas because it eats to much memory... > I think i will take a quadcore with 4gb ram. > > > Am 07.07.2014 um 13:31 schrieb Reindl Harald <[email protected]>: > >> >> >> Am 07.07.2014 13:26, schrieb Eero Volotinen: >>> Well, we are currently running two physical scanner servers and one >>> very large amazon instance for our PCI scanners .. >>> >>> Usually servers are running quad core processor and 32GB to 128GB of >>> physical memory. >>> So, it's based on my experiences on real production environments. >> >> no it's not >> >> experience would be "we tried it with less RAM but we had to >> upgrade to 32 GB because it otherwise did not work" and not >> "you need that much RAM because i have" >> >> the most RAM is needed for the feed-sync and with 3 GB you are normally >> fine > > > > Yes you are right, most of the time it will be a default scan config. It´s > okay if its not parallel, but it should not run just one scan a night. > >> >> Do you need to run a lot of scans in parallel, or can a scan run lazily >> all night? >> Do you want to brute force / enumerate logins, or do you "just" run >> discovery scans. >> Etc etc > > Thanks for your fast responses, > Rene > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > ------------------------------ Geoff Galitz http://www.galitz.org _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
