Hacker News Reader

nerfborpiton 90x Faster Than Pgvector – Lantern's HNSW Index Creation Time

External index creation also requires that a significant amount of data be in the table for it to be worth it, along with all the other potential issues.

nerfborpiton 90x Faster Than Pgvector – Lantern's HNSW Index Creation Time

Using ivfflat is much faster for bulk index creation than lantern. There are a lot of trade offs depending on what everyone's specific use case is, but it seems like a pretty massive thing to leave out.

``` postgres=# CREATE INDEX ON sift USING ivfflat (v vector_l2_ops) WITH (lists=1000); CREATE INDEX Time: 65697.411 ms (01:05.697) ```

nerfborpiton 90x Faster Than Pgvector – Lantern's HNSW Index Creation Time

This reads like a marketing piece, not an honest technical blogpost.

I agree that Usearch is fast, but it feels pretty dishonest to take credit for someone else's work. Like maybe at least honestly profile what's going on with USearch vs pgvector (..and which settings for pgvector??), and write something interesting about it?

The last time I tried Lantern, it'd segfault when I tried to do anything non-trivial with it, and was incredibly unsafe with how it handled memory. Hopefully that's at least fixed.. but lantern has so many red flags.