aboutsummaryrefslogtreecommitdiff
path: root/benchmarks/benchmarks.md
diff options
context:
space:
mode:
authorSebastiano Tronto <sebastiano@tronto.net>2025-12-17 17:36:16 +0100
committerSebastiano Tronto <sebastiano@tronto.net>2025-12-17 17:36:16 +0100
commitec9593e2ff0856d78b37df3a977a753be82bfddc (patch)
tree684dad42207f48125db40ce0afb32046cdba1726 /benchmarks/benchmarks.md
parentac3a91f4f173e7a38c70d5cd0caf5a025642312b (diff)
downloadnissy-core-ec9593e2ff0856d78b37df3a977a753be82bfddc.tar.gz
nissy-core-ec9593e2ff0856d78b37df3a977a753be82bfddc.zip
Fix alignment
Diffstat (limited to 'benchmarks/benchmarks.md')
-rw-r--r--benchmarks/benchmarks.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/benchmarks/benchmarks.md b/benchmarks/benchmarks.md
index adc3377..ddcb91f 100644
--- a/benchmarks/benchmarks.md
+++ b/benchmarks/benchmarks.md
@@ -247,3 +247,8 @@ Time per cube adjusted for table size (in seconds \* GiB, lower is better).
247* For H48, both GCC and Clang have been tried, with the same options; 247* For H48, both GCC and Clang have been tried, with the same options;
248 the resulting executable was about 10% faster with GCC compared to Clang. 248 the resulting executable was about 10% faster with GCC compared to Clang.
249 vcube only supports compiling with Clang. 249 vcube only supports compiling with Clang.
250* The performance of the H48 solver depends slightly, but measurably, on the
251 alignment of the pruning table in memory. This is not handled by the core
252 library, but by the program that uses it. For these tests, we have used as
253 reference implementation the program in `tools/301_solve_file`, which
254 ensures 64-byte alignment.

Generated with cgit - Back to sebastiano.tronto.net