Hi James,
On Sep 25, 2008, at 7:07 PM, James Birk wrote:
> Darnit, didn't you guys say just a couple of years ago that Nessus was
> NEVER to be run on VMware virtual machines, because it's so horribly
> slow when you do that? What changed?
Nessus 3.2 has been optimized to reduce several operations which were
slow on VMware. System calls and memory copies have been greatly
reduced, and therefore it performs much better than Nessus 3.0 did
(and obviously 2.x). This is why you do not get the VMware warning any
more when you start Nessus 3.2 in a virtualized environment.
Also, VMware deployments are much more mature now than what they used
to be several years ago, and is generally done on much beefier
hardware. A lot of production services are running on top of ESX
today, and we believe that Nessus can safely be added there.
Of course, if you have the choice between running Nessus natively on
beefy hardware, or virtualized on top of this same hardware, you will
get better performance natively. However, the difference between
native and virtualized won't be as glaring with 3.2 as what it used to
be.
-- Renaud
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
