honggfuzz allows for binding to a CPU with --pin_thread_cpu=1
however it is very ineffective/naive about this, it always binds the same CPUs, even if multiple honggfuzz fuzzing campaigns are running.
As long as not more than 2 fuzzing campaigns are running, this options would be beneficial to have. (because of all the locking honggfuzz cannot achieve 100% load on a thread like afl++). but with 3+ campaign this would make fuzzing with honggfuzz worse.
maybe lets have this as an option, default on?
also important is for that not to impact AFL++, first honggfuzz has to be started and then afl-fuzz, as afl-fuzz binds to unused CPUs (and honggfuzz doesnt care).
honggfuzz allows for binding to a CPU with --pin_thread_cpu=1
however it is very ineffective/naive about this, it always binds the same CPUs, even if multiple honggfuzz fuzzing campaigns are running.
As long as not more than 2 fuzzing campaigns are running, this options would be beneficial to have. (because of all the locking honggfuzz cannot achieve 100% load on a thread like afl++). but with 3+ campaign this would make fuzzing with honggfuzz worse.
maybe lets have this as an option, default on?
also important is for that not to impact AFL++, first honggfuzz has to be started and then afl-fuzz, as afl-fuzz binds to unused CPUs (and honggfuzz doesnt care).