Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speed up the analysis with new cwe_checker:stable docker image #392

Closed
ZeroXLN opened this issue Feb 28, 2023 · 2 comments
Closed

Speed up the analysis with new cwe_checker:stable docker image #392

ZeroXLN opened this issue Feb 28, 2023 · 2 comments

Comments

@ZeroXLN
Copy link

ZeroXLN commented Feb 28, 2023

Hello, I want to speed up the analysis with cwe_checker:stable docker image, I pull image from docker pull fkiecad/cwe_checker:stable.
It spends a lot time when analyzing one binary file. I saw the Issues [Issue #240] and Discussions[Discussions #260], they all mentioned to run multiple instances in parallel. But I want to run multiple instances for the same file to analyze, the new cwe_checker:stable is command-like, like this.
image

Can anyone give me the details on parallelization? Thanks!

@Enkelmann
Copy link
Contributor

Right now parallelization of the analysis for a single binary is simply not implemented. And unfortunately, at the moment I do not know when I will find the time to implement this.

But how long does analysis of a single binary take for you? For small binaries it should not take more than 15 minutes in my experience. I am aware of some cases, where the cwe_checker takes significantly more time and RAM. But these are usually due to bugs in the cwe_checker code. I do not often test larger binaries, as they are usually written in C++, where the cwe_checker analysis can be very imprecise due to not yet implemented features.

@Enkelmann
Copy link
Contributor

Closing, since I never heard back from the issue author.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants