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
We've benchmarked SemHash on a variety of datasets to measure the deduplication performance and speed. The benchmarks were run with the following setup:
409
-
- The benchmarks were all run on CPU
410
-
- The benchmarks were all run with the default ANN backend (usearch)
411
-
- The used encoder is the default encoder ([potion-base-8M](https://huggingface.co/minishlab/potion-base-8M)).
412
-
- The timings include the encoding time, index building time, and deduplication time.
413
-
### Train Deduplication Benchmark
414
-
415
-
| Dataset | Original Train Size | Deduplicated Train Size | % Removed | Deduplication Time (s) |
As can be seen, SemHash is extremely fast, and scales to large datasets with millions of records. There are some notable examples of train/test leakage, such as `enron_spam` and `student`, where the test dataset contains a significant amount of semantic overlap with the training dataset.
460
-
461
-
### Reproducing the Benchmarks
462
-
463
-
To run the benchmarks yourself, you can use the following command (assuming you have the `datasets` library installed):
408
+
SemHash is extremely fast and scales to large datasets with millions of records. We've benchmarked both single-dataset deduplication and train/test deduplication across a variety of datasets. For example, deduplicating 1.8M records takes only ~83 seconds on CPU.
464
409
465
-
```bash
466
-
python -m benchmarks.run_benchmarks
467
-
```
468
-
Optionally, the datasets can be updated in the [data.py](https://github.com/MinishLab/semhash/blob/main/benchmarks/data.py) file.
410
+
For detailed benchmark results including performance metrics across 17 datasets, see the [benchmarks directory](benchmarks/README.md).
This directory contains the benchmarking code and results for SemHash. The benchmarks measure deduplication performance and speed across a variety of datasets.
4
+
5
+
## Setup
6
+
7
+
All benchmarks were run with the following configuration:
8
+
-**CPU-only**: All benchmarks run on CPU (no GPU acceleration)
0 commit comments