diff options
| author | Andrea Fioraldi <andreafioraldi@gmail.com> | 2019-10-23 19:48:26 +0200 |
|---|---|---|
| committer | Andrea Fioraldi <andreafioraldi@gmail.com> | 2019-10-23 19:48:26 +0200 |
| commit | 0f032266562115092100bc54b5f780a4aeb15c56 (patch) | |
| tree | a8f1e1b9030cde8ba4bf1321818d65a1486c9abe /docs | |
| parent | 297e9e3cf59540f16b8260a01ef7c6cd01d9e554 (diff) | |
| parent | 39b7f488705a7e242b7a54695ca8e03fb2e73d81 (diff) | |
| download | afl++-0f032266562115092100bc54b5f780a4aeb15c56.tar.gz | |
Merge branch 'master' of github.com:vanhauser-thc/AFLplusplus
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/perf_tips.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/perf_tips.txt b/docs/perf_tips.txt index 215895b6..2fa19234 100644 --- a/docs/perf_tips.txt +++ b/docs/perf_tips.txt @@ -50,6 +50,9 @@ Even if you don't have a lightweight harness for a particular target, remember that you can always use another, related library to generate a corpus that will be then manually fed to a more resource-hungry program later on. +Also note that reading the fuzzing input via stdin is faster than reading from +a file. + 3) Use LLVM instrumentation --------------------------- @@ -161,6 +164,11 @@ and not waste CPU time. There are several OS-level factors that may affect fuzzing speed: + - If you have no risk of power loss then run your fuzzing on a tmpfs + partition. This increases the performance noticably. + Alternatively you can use AFL_TMPDIR to point to a tmpfs location to + just write the input file to a tmpfs. + - High system load. Use idle machines where possible. Kill any non-essential CPU hogs (idle browser windows, media players, complex screensavers, etc). |
