diff options
author | van Hauser <vh@thc.org> | 2020-05-15 09:27:15 +0200 |
---|---|---|
committer | van Hauser <vh@thc.org> | 2020-05-15 09:27:15 +0200 |
commit | d536ddc24085bced267143b4f45102715d71693e (patch) | |
tree | 7028606718ed9e4bb0c8d11406ef9c6e4856ba94 /docs/parallel_fuzzing.md | |
parent | 564399bd754e355d28da5b498856c05b63901661 (diff) | |
download | afl++-d536ddc24085bced267143b4f45102715d71693e.tar.gz |
change: slaves only sync from masters
Diffstat (limited to 'docs/parallel_fuzzing.md')
-rw-r--r-- | docs/parallel_fuzzing.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/parallel_fuzzing.md b/docs/parallel_fuzzing.md index 8b39df04..12aefb46 100644 --- a/docs/parallel_fuzzing.md +++ b/docs/parallel_fuzzing.md @@ -57,12 +57,14 @@ Each fuzzer will keep its state in a separate subdirectory, like so: Each instance will also periodically rescan the top-level sync directory for any test cases found by other fuzzers - and will incorporate them into its own fuzzing when they are deemed interesting enough. +For performance reasons only -M masters sync the queue with everyone, the +-S slaves will only sync from the master. The difference between the -M and -S modes is that the master instance will still perform deterministic checks; while the secondary instances will -proceed straight to random tweaks. If you don't want to do deterministic -fuzzing at all, it's OK to run all instances with -S. With very slow or complex -targets, or when running heavily parallelized jobs, this is usually a good plan. +proceed straight to random tweaks. + +Note that you must always have one -M master instance! Note that running multiple -M instances is wasteful, although there is an experimental support for parallelizing the deterministic checks. To leverage |