about summary refs log tree commit diff
path: root/docs/perf_tips.txt
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2019-10-23 17:01:05 +0200
committervan Hauser <vh@thc.org>2019-10-23 17:01:05 +0200
commit39b7f488705a7e242b7a54695ca8e03fb2e73d81 (patch)
tree16eb0d16c070601b52777565a200978b333017f1 /docs/perf_tips.txt
parentb9bc81544a438868529fbe040f4734256dce7a1d (diff)
downloadafl++-39b7f488705a7e242b7a54695ca8e03fb2e73d81.tar.gz
performance doc enhancements
Diffstat (limited to 'docs/perf_tips.txt')
-rw-r--r--docs/perf_tips.txt8
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).