Live data from Hacker News

Show HN: TurboQuant-WASM – Google's vector quantization in the browser

11–12 of 12 posts

Re: Show HN: TurboQuant-WASM – Google's vector quantization in the browser

#11

Post by ninja3925 » Sun, Apr 05, 2026, 1:05 AM UTC

netdur wrote: post #9

I tried TQ for vector search and my findings is not good, it is not worth it if you cannot use GPU, however I got same quality of search as 32f using 8bit quant I wrote ann ext for sqlite, using tq, I do save a lot on space but 32f is still faster despite everything I have tried code here https://github.com/netdur/munind/tree/main/src/tq

So i assumed it would get crushed by OPQ (which requires training)

Re: Show HN: TurboQuant-WASM – Google's vector quantization in the browser

#12

Post by teamchong » Wed, Apr 08, 2026, 7:09 AM UTC

refulgentis wrote: post #8

Sloppiest slop I've seen in a couple weeks: - fork of a fork of a quantization technique - Only contribution is...compiling JS to WASM by default? - suspicious burst of ~nothing comments from new accounts - 6 comments 7 hours in, 4 flagged/dead, other 2 also spammy, confused and making category errors at best, at worst, more spam. - Demo shows it's worse : 800 ms instead of 2.6 ms for text embedding search - "but it…

I made some adjustment, can you try again? Is it faster now?

https://teamchong.github.io/turboquant-wasm/search.html

Post reply on HN