Knowledge base for plugins about risu HOT 7 CLOSED

What do you mean by plugin info? The plugins table?

I use the tool 1 database per assessment.

from risu.

Yes, the plugins table. I just loaded another scan and it took 30 minutes to load. Just thinking that if the plugins could be stored in a "common" database that is used by all of the scans (assuming the scans were in different databases) then the load of new scans could be much faster as it could just check to see if the plugin data existed in the common set and if not then load it up. I know that the plugin output depends on the host but the rest is common. Would this help the load time? Is it something that would be worth looking at?

from risu.

How many hosts do you have in the .nessus file for it to take 30 minutes to load? I parse about 5000 in less than 5 minutes.

from risu.

Do you have any more information about this?

from risu.

I have 444 hosts with 38712 risks in the .nessus file. Seems each risk has to be parsed independently of all others and the common metadata is not just referenced.

from risu.

The parser does a find_or_create_by_id() on each plugin. There should only be 1 entry for each plugin in the plugins table. The risks are unique for the most part, while they do contain some overlapped data, plugin_output should be unique per Host/ReportItem.

References on the other hand are just a create() and I will fix that to be a find_or_create..() that may speed some things up. Expect that in v1.5.1.

What database adapter are you using? SQLite3 performance wouldn't be that great on that size of a dataset. Mysql should be faster by far.

from risu.

Hmmm. I am using MySQL and the speed is a real issue. Understood on the find_or_create_by_id() call. Maybe it is an issue with the speed to query the database for the find part of that call. Is there an index on the key you are using to look up the id? If not, maybe an index added to the create table statement might help.

from risu.