Differences

This shows you the differences between two versions of the page.

--- usb-devices:onerng [2020/06/16 18:34] – [Create a 10M file] chuck
+++ usb-devices:onerng [2020/06/16 19:29] (current) – [Installing software] chuck
@@ Line 44: / Line 44: @@
 You can (and should) verify what I typed here at the Official Site:
 http://onerng.info/onerng/
+----
 ====rng-tools service====
@@ Line 354: / Line 356: @@
 ===Results===
-The results show that using ''%%/dev/ttyACM0%%'', which is the OneRNG, is faster than using ''%%/dev/random%%'' which also uses the OneRNG. Judging by the **ent** tests below, the data for tty.img and random.img produce similar results.
+The results show that using ''%%/dev/ttyACM0%%'' is roughly 3x faster than using ''%%/dev/random%%'' while both are much slower than ''%%/dev/urandom%%''.
+^ Stat ^ /dev/random ^ /dev/ttyACM0 ^ /dev/urandom ^
+^ real | 9m55.880s   | 3m2.079s     | 0m0.056s     |
+^ user | 0m0.028s    | 0m0.092s     | 0m0.000s     |
+^ sys  | 0m4.308s    | 0m1.016s     | 0m0.056s     |
 ----
+====entropy_avail====
+You can check the amount of entropy available by reading the file ''%%/proc/sys/kernel/random/entropy_avail%%''.
+<WRAP announcement green>
+Here's a oneliner I wrote to monitor it from another terminal while I ran the above tests:
+<code>
+while true; do cat /proc/sys/kernel/random/entropy_avail; sleep 1; done
+</code>
+</WRAP>
+I noticed that while idle and with the OneRNG plugged in, the value stayed above 2500 and would climb well past 3000 if left alone for a while. The max value can be found in ''%%/proc/sys/kernel/random/poolsize%%'' (where mine is set at 4096).
+  * When running from ''%%/dev/random%%'', the **entropy_available** quickly depletes until the task is finished.
+    * When the OneRNG **is** plugged in, it instantly regenerates to above 2000 once the task is finished.
+    * When the OneRNG ** is not** plugged in, it slowly starts rising once the task is finished.
+  * When running from ''%%/dev/ttyACM0%%'', the **entropy_available** seems to stay the same while creating the 10M file.
+  * When running from ''%%/dev/urandom%%'', the **entropy_available** seems to stay the same while creating the 10M file.
+----
 ====ent====