Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Nessus 3.0 released |
|---|---|
| Date: | Tue, 13 Dec 2005 15:54:55 -0500 |
On Dec 13, 2005, at 15:43, Erin Carroll wrote:
One key performance issue I've run into (and I'm prbably not alone here)
is the inability to easily manage the nessus server-side resource
utilization when working with large numbers of hosts. While you can of
course limit the number of consecutive scans, or even nice nessusd itself,
there are many cases where the resource bottleneck is due to a particular
plugin or a well filtered host (as you allude). Is there capability within
the engine itself (or plans to implement) a way for nessusd to set
resource limits that don't rely on variables like the # of scanned
hosts/concurrent scan threads? I.e. nessus can use up to X %age of
available memory/cpu/IO and self-throttle.
-- Renaud
-- Renaud Deraison http://www.nessus.org http://www.tenablesecurity.com
http://www.securityfocus.com/sponsor/pen-test_050831 -------------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Full-disclosure] Inside AV engines?, AgentSmith15 |
|---|---|
| Next by Date: | RE: Nessus 3.0 released, Josh Perrymon |
| Previous by Thread: | Re: Nessus 3.0 released, Erin Carroll |
| Next by Thread: | RE: Nessus 3.0 released, Josh Perrymon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |