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: API.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,14 @@ SELECT vector_backend();
57
57
**Returns:**`TEXT`
58
58
59
59
**Description:**
60
-
Returns the active backend used by TurboQuant lookup-table scans. This is useful when validating that TurboQuant is using the expected SIMD path on a target runtime.
60
+
Returns the SIMD tier selected at load time, the same one `vector_backend()` reports.
61
+
62
+
TurboQuant lookup-table scans no longer vary by backend: the scan is one table lookup
63
+
per row, which is already about one load per cycle on any machine, and NEON has no
64
+
gather instruction at all. A single implementation is used everywhere, so the same query
65
+
returns the same distance whatever the CPU — the per-backend versions this replaced
66
+
differed by up to 1.5e-4 relative because they accumulated in `float` while the scalar
0 commit comments