korben99 commited on
Commit
cf2bf5c
·
verified ·
1 Parent(s): c00510c

Add model card

Browse files
Files changed (1) hide show
  1. README.md +3 -1
README.md CHANGED
@@ -22,7 +22,7 @@ Native **4096-bit binary** embedding model from the **Binary Native Embeddings**
22
  |---|---|---|---|
23
  | 0.7275 | 0.2958 | 500 KB | 6.0x faster at 1M vecs (FAISS AVX2+POPCNT, Intel Core Ultra 7) |
24
 
25
- Part of [binary-native-embeddings](https://github.com/korben99/binary-native-embeddings-for-CPU-Retrieval).
26
 
27
  ## Why binary?
28
 
@@ -33,6 +33,8 @@ At 1M vectors with FAISS `IndexBinaryFlat` (AVX2 + POPCNT, Intel Core Ultra 7):
33
 
34
  POPCNT processes 64 bits/cycle; 2048-bit Hamming distance = 32 POPCNT instructions vs 384 multiply-accumulates, plus 6× better cache utilization (256 bytes/vector vs 1 536 bytes).
35
 
 
 
36
  ## Usage
37
 
38
  ```python
 
22
  |---|---|---|---|
23
  | 0.7275 | 0.2958 | 500 KB | 6.0x faster at 1M vecs (FAISS AVX2+POPCNT, Intel Core Ultra 7) |
24
 
25
+ Part of [binary-native-embeddings-for-CPU-Retrieval](https://github.com/korben99/binary-native-embeddings-for-CPU-Retrieval) · [Discussion](https://discuss.huggingface.co/t/native-binary-embeddings-experiment-curious-about-your-thoughts/177107)
26
 
27
  ## Why binary?
28
 
 
33
 
34
  POPCNT processes 64 bits/cycle; 2048-bit Hamming distance = 32 POPCNT instructions vs 384 multiply-accumulates, plus 6× better cache utilization (256 bytes/vector vs 1 536 bytes).
35
 
36
+ > **Note:** float uses `IndexFlatIP` (cosine similarity) and binary uses `IndexBinaryFlat` (Hamming distance) — different metrics, but timings are comparable for measuring ranking latency at scale.
37
+
38
  ## Usage
39
 
40
  ```python