diff options
| author | vanhauser-thc <vh@thc.org> | 2023-11-20 09:56:09 +0100 |
|---|---|---|
| committer | vanhauser-thc <vh@thc.org> | 2023-11-20 09:56:09 +0100 |
| commit | aabbdac86d6215833391a54fa7d3a474ad41e3fd (patch) | |
| tree | bfa87caca6e4457b0cf5d9db4348f2b784d9e332 /benchmark/README.md | |
| parent | 5681267bbc901941e6056390abfe6aad43b45775 (diff) | |
| download | afl++-aabbdac86d6215833391a54fa7d3a474ad41e3fd.tar.gz | |
add benchmarks
Diffstat (limited to 'benchmark/README.md')
| -rw-r--r-- | benchmark/README.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/benchmark/README.md b/benchmark/README.md index e37abad2..c7d75e42 100644 --- a/benchmark/README.md +++ b/benchmark/README.md @@ -9,6 +9,14 @@ To achieve this, we use a sample program ("test-instr.c") where each path is equally likely, supply it a single seed, and tell AFL to exit after one run of deterministic mutations against that seed. +**Note that this is not a real-world scenario!** +Because the target does basically nothing this is rather a stress test on +Kernel I/O / context switching. +For this reason you will not see a difference if you run the multicore test +with 20 or 40 threads - or even see the performance decline the more threads +(`-f` parameter) you use. In a real-world scenario you can expect to gain +exec/s until 40-60 threads (if you have that many available on your CPU). + Usage example: ``` |
