-
Notifications
You must be signed in to change notification settings - Fork 302
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
Investigate high fuzzer overhead #174
Comments
I also get high overhead after a day or so when using
|
You'd probably need to use some kind of profiler (e.g. perf on Linux) to figure out where the CPU time is spent, and if there's a bug there that we can fix. Alternatively, you can use network synchronization (and maybe a low |
I did some initial investigation a couple weeks ago, using perf to trace a long running session. The largest win was switching to Fuzzilli was also spending a significant amount of compute in the JavascriptLifter, in inlining and determining which variables should be |
Oh wow, great find! Yeah, using I'll put together a PR to switch to
|
Since commit 1408aab, Fuzzilli computes and displays the "fuzzer overhead", i.e. the fraction of time that is not spent executing JavaScript code in the target engine. Normal values seem to be roughly between 5% and 15%. However, in long fuzzing sessions and seemingly especially in multithreaded mode (e.g. --jobs=32), this number can become quite significant (approaching 50%). This should be investigated.
The text was updated successfully, but these errors were encountered: