commit 2048e5a99de981a53d5eeb8a66d98e281898c9f0
parent eb89f4c234e5d3868ad33223684934a30c76393e
Author: Sebastiano Tronto <sebastiano@tronto.net>
Date: Thu, 19 Jun 2025 23:00:47 +0200
Add small comments on benchmark results
Diffstat:
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/benchmarks/benchmarks.md b/benchmarks/benchmarks.md
@@ -216,6 +216,14 @@ Time per cube adjusted for tables size (in seconds \* GiB, lower is better).
|H48 h7 k2 | 3.6GiB | 1.30 | 15.26 | | |
|H48 h6 k2 | 1.8GiB | 1.24 | 14.76 | | |
+## Comments on the results
+
+* Adjusting for table size, vcube generally is a bit faster than H48,
+ except for 20 moves scrambles where H48 is a clear winner.
+* On sets of 25 scrambles, H48 performs better than vcube when using
+ multiple threads. However, this advantage will likely disappear (or
+ even invert) if we increase the size of the set.
+
## Other notes
* Missing values in the table mean that the test is very slow and I did