Audit library should use parallelism instead of asynchronous operations for performance when appropriate like when running in the CLI. about devaudit HOT 4 CLOSED

One problem with the command line client running multiple server requests at a time is in theory it could reduce the number of concurrent users. For example, if the server can support ten requests at a time and one client uses up all ten requests, then we can only support one user. If on the other hand the client performs sequential requests then we can support ten users.

from devaudit.

I was thinking of adding some additional options like maybe MaxPackagesQuery and MaxVulnsQuery and DisableConcurrentQueries so the user can control the size of individual queries sent and the number of parallel queries made on the back-end, which would allow us to troubleshoot backend issues. This would be important when using 3rd-pary backends like vulnersdb. The parallelism is all internal to the GetVulnerabiltiesApiv2() method so it shouldn't be too difficult to change the behavior based on options the user passes.

from devaudit.

This definitely sounds like a reasonable idea. I have no particular leaning one way or another whether these are mentioned in the help text or not. I am fine with keeping them "secret" for testing, or publishing them so that users can tune things themselves should they be so inclined.

from devaudit.

Ok the new parallelism is implemented and has been running for the past couple of weeks and seems to be ok. I'm closing this and opening a new enhancement issue for the additional parallelism options.

from devaudit.