diff options
| author | Andrea Fioraldi <andreafioraldi@gmail.com> | 2020-02-03 13:02:16 +0100 |
|---|---|---|
| committer | Andrea Fioraldi <andreafioraldi@gmail.com> | 2020-02-03 13:02:16 +0100 |
| commit | e2eedefc65bec1a04605f117a11ca8bdf9d80323 (patch) | |
| tree | 653e28fb2f74790ff35706c9c93ce91893f5a3a2 /docs/perf_tips.txt | |
| parent | fd03c64346ab3f63fc5ceafd891dee245121b5c9 (diff) | |
| download | afl++-e2eedefc65bec1a04605f117a11ca8bdf9d80323.tar.gz | |
docs to md
Diffstat (limited to 'docs/perf_tips.txt')
| -rw-r--r-- | docs/perf_tips.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/perf_tips.txt b/docs/perf_tips.txt index 0cac8f7b..b4a8893d 100644 --- a/docs/perf_tips.txt +++ b/docs/perf_tips.txt @@ -140,7 +140,7 @@ options to use non-instrumented system-wide copies instead. The fuzzer is designed to need ~1 core per job. This means that on a, say, 4-core system, you can easily run four parallel fuzzing jobs with relatively -little performance hit. For tips on how to do that, see parallel_fuzzing.txt. +little performance hit. For tips on how to do that, see parallel_fuzzing.md. The afl-gotcpu utility can help you understand if you still have idle CPU capacity on your system. (It won't tell you about memory bandwidth, cache |