You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Can anyone give me the details on parallelization? Thanks!
The text was updated successfully, but these errors were encountered:
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.
Hello, I want to speed up the analysis with cwe_checker:stable docker image, I pull image from
![image](https://user-images.githubusercontent.com/58169480/221765855-75e4ef59-515f-45e1-8e00-100aa38b783c.png)
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.
Can anyone give me the details on parallelization? Thanks!
The text was updated successfully, but these errors were encountered: