Am 08.01.2017 um 03:19 schrieb Fábio Fernandes:
In my opinion i think that those resources would be better spent on openvassd
process since it does the heavy lifting.
when the bottleneck are shared ressources used by openvassd it can't do
anyhting about it and so you need to get rid of the concurrecncy by just
have more of this ressources aka more instances
No dia 08/01/2017, às 00:59, Reindl Harald <[email protected]> escreveu:
Am 08.01.2017 um 01:30 schrieb TN TN:
HI Christian, I actually have it installed with postgresql, but when
you're scanning thousands of internal hosts on a weekly basis it slows
it down considerably over time.. I'm just curious on why openvasmd is
not using enough resources on the server. Thanks TN
because they are not available which means you assume the bottleneck likely
where it isn't - when you scan thousands of hosts how do you come to the
conclusion at a single openvas machine will be enough?
just install *more* instances as virtual machines when you say you are not
cpu-bound and have enough memory and spread the load - problem solved
On 7 January 2017 at 17:09, Christian Fischer
<[email protected]
<mailto:[email protected]>> wrote:
Hi,
On 07.01.2017 19:43, TN TN wrote:
> Hi, I have a fairly powerful server and it seems like the openvasmd
> process isnt using up alot of the resources on the box. If I run
> numerous scans (the scanner being off of the main openvasmd
server), the
> openvasmd process barely uses any resources, however Greenbone slows
> down and the backend commands take much longer to execute. Is there a
> way to force openvasmd to use more resources (CPU/Memory) so that it
> runs faster? Thanks, TN
i don't think this is possible and it also probably wouldn't help here.
The manager process is using the resources it needs.
I think the bottle neck is more likely the sqlite database backend which
slows down if multiple scanners are sending data to the manager. Have a
look at the postgresql database backend which might help to improve the
performance.
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
