-
Notifications
You must be signed in to change notification settings - Fork 386
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
[Bug-Candidate]: Maximize CPU output when running fuzzer #1207
Comments
Can you check if this a regression from a previous version? I think @elopez reproduced this with the current version as well. |
This applies to previous builds as well – or at least the branches for fixes on Curvance between 2.2.2 and 2.2.3. |
@aviggiano hi! what version are you testing with? Can you check if there is any improvement with a build from PRs #1243 or #1245? |
hi @elopez |
@aviggiano any updates? You can also re-test with the latest |
Hey |
Thanks, |
Personally, I'm getting better result on testing |
Hey Much better than before! But still not 100% 🤔 ![]() I'm using this build https://github.com/crytic/echidna/actions/runs/9095717896/job/24999535164?pr=1245 |
Can you make num workers 2 times the number of cores? :-P |
@aviggiano can you try again using |
Hey @ggrieco-tob sorry but I'm OOO for the month, I won't be able to test this for some time |
Describe the issue:
When deployed on a 16 core machine, with 15 workers, the CPU usage seems to be maxed at about 40-50%. When deployed on an 8 core machine, with 7 workers, CPU usage has only ever hit a max of around 65%.
Code example to reproduce the issue:
Follow instructions for reproduction here, and if testing on cloudexec, then run
make ec
(for echidna-cloud) ormake el
(echidna-local).https://github.com/curvance/Curvance-CantinaCompetition/tree/CodeFAQAndAdjustments/tests/fuzzing
Version:
Echidna 2.23 & previous
Relevant log output:
No response
The text was updated successfully, but these errors were encountered: