You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-14Lines changed: 0 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,16 +100,6 @@ For a testing environment, use the following instead:
100
100
101
101
(NOTE: Beware that the software will result in a much slower execution when running in debug mode and using sanitizers. Use this only for debug purposes, not to run performance tests.)
102
102
103
-
### Enable All Encoders
104
-
105
-
By default, you can choose between three encoders to compress the PTHash
106
-
data structure (see the output of `./build --help` for suggestions).
107
-
108
-
If you want to test all the encoders we tested in the papers,
109
-
compile again with
110
-
111
-
cmake .. -D PTHASH_ENABLE_ALL_ENCODERS=On
112
-
113
103
### Enable Large Bucket-Id Type
114
104
115
105
By default, PTHash assumes there are less than $2^{32}$ buckets, hence 32-bit integers are used
@@ -233,10 +223,6 @@ Giulio on 13/04/2025: Update this section with new benchmarks.
233
223
234
224
<!-- The script `script/run_benchmark.sh` runs some trade-off configurations (encoder, $\alpha$, $\lambda$) that have been tested in the papers, on 100M and 1000M keys.
235
225
236
-
Be sure you run the benchmark after compiling with
237
-
238
-
cmake .. -D PTHASH_ENABLE_ALL_ENCODERS=On
239
-
240
226
From within the directory where the code has been compiled, just run
0 commit comments