OVAL Vulnerability Template is time consuming

[GoogleCodeExporter]

When starting a vulnerability scanning using OVAL and 
windows.vulnerability.xml, this could take a long time. 

This is not an issue but due to the large xml file processed. The oval 
interpreter takes a long time to collect value and analyze information. This is 
by the far the most annoying thing is OVAL.

You may also notice that ovaldi consumes a huge amount of CPU and memory !!

Please, report me any crash due to ovaldi. I will be happy to rely it to the 
oval mitre dev team.

Original issue reported on code.google.com by [email protected] on 5 Dec 2010 at 4:27

[GoogleCodeExporter]

Original comment by [email protected] on 5 Dec 2010 at 4:32

• Changed state: New