[prev in list] [next in list] [prev in thread] [next in thread]
List: openvas-discuss
Subject: Re: [Openvas-discuss] RAM usage limitation
From: Paula_Gonzalez_Muñoz <p.gonmu () gmail ! com>
Date: 2013-12-12 6:48:06
Message-ID: CAHNJ+mAj+XQDJHcdoWwxEU_ZC9DCy=AmEs-WGv6mLCHAvFv7ZA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi,
I have tested on several servers with 2 or 3 GB + 1 of swap. Yesterday I
was monitoring with htop and, when scanning a single host, free RAM would
go from 1.5Gb to 20 MB depending on the vulnerability scanned.
2013/12/11 Russell Jones <russell-list@jonesmail.me>
> We have found it takes roughly 100MB of memory per host at a time when
> doing nmap scans + full & deep ultimate vulnerability tests.
>
> What are the server specs you are running this on?
>
>
> On 12/9/2013 9:03 AM, William Scott Lockwood III wrote:
>
>> On Mon, Dec 9, 2013 at 8:57 AM, Paula Gonzalez Muñoz <p.gonmu@gmail.com>
>> wrote:
>>
>>> I have found that the synchronization does not cause any problem... and
>>> scanning target by target is not really a solution for us since we have
>>> to
>>> perform scans out of office hours on over 30 servers (and increasing).
>>>
>>> Regards,
>>> Paula
>>>
>> Target by target isn't the issue. Define your range (30 servers is
>> tiny compared to what I'm scanning) but limit the number of concurrent
>> hosts and concurrent NVT's until you find a balance that works for
>> you. Currently, I limit mine to 5 hosts with 4 concurrent NVT's and
>> have no problems running scans from a VM.
>> _______________________________________________
>> Openvas-discuss mailing list
>> Openvas-discuss@wald.intevation.org
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/
>> openvas-discuss
>>
>
> _______________________________________________
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
--
Paula González Muñoz
[Attachment #5 (text/html)]
<div dir="ltr"><div>Hi,<br><br></div>I have tested on several servers with 2 or 3 GB \
+ 1 of swap. Yesterday I was monitoring with htop and, when scanning a single host, \
free RAM would go from 1.5Gb to 20 MB depending on the vulnerability scanned.<br> \
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/11 Russell \
Jones <span dir="ltr"><<a href="mailto:russell-list@jonesmail.me" \
target="_blank">russell-list@jonesmail.me</a>></span><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> We have found it takes roughly 100MB of memory per host at a \
time when doing nmap scans + full & deep ultimate vulnerability tests.<br> <br>
What are the server specs you are running this on?<div><div class="h5"><br>
<br>
On 12/9/2013 9:03 AM, William Scott Lockwood III wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div><div class="h5"> On Mon, Dec 9, 2013 at 8:57 AM, \
Paula Gonzalez Muñoz <<a href="mailto:p.gonmu@gmail.com" \
target="_blank">p.gonmu@gmail.com</a>> wrote:<br> <blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I have found \
that the synchronization does not cause any problem... and<br> scanning target by \
target is not really a solution for us since we have to<br> perform scans out of \
office hours on over 30 servers (and increasing).<br> <br>
Regards,<br>
Paula<br>
</blockquote>
Target by target isn't the issue. Define your range (30 servers is<br>
tiny compared to what I'm scanning) but limit the number of concurrent<br>
hosts and concurrent NVT's until you find a balance that works for<br>
you. Currently, I limit mine to 5 hosts with 4 concurrent NVT's and<br>
have no problems running scans from a VM.<br></div></div><div class="im">
______________________________<u></u>_________________<br>
Openvas-discuss mailing list<br>
<a href="mailto:Openvas-discuss@wald.intevation.org" \
target="_blank">Openvas-discuss@wald.<u></u>intevation.org</a><br> <a \
href="https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss" \
target="_blank">https://lists.wald.intevation.<u></u>org/cgi-bin/mailman/listinfo/<u></u>openvas-discuss</a><br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
Openvas-discuss mailing list<br>
<a href="mailto:Openvas-discuss@wald.intevation.org" \
target="_blank">Openvas-discuss@wald.<u></u>intevation.org</a><br> <a \
href="https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss" \
target="_blank">https://lists.wald.intevation.<u></u>org/cgi-bin/mailman/listinfo/<u></u>openvas-discuss</a></div></div></blockquote></div>
<br><br clear="all"><br>-- <br><div dir="ltr"><div> Paula González \
Muñoz</div><div><br></div><div> </div><div> </div></div> </div>
_______________________________________________
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic