Hacker News Reader

Title:

> 300μs typo correction for 1.3M words

Article:

> 300μs for correctly spelled queries and ~5ms/word for misspellings

Aren't these contradictory?

The important number that changed here was the 30ms to 300μs for correctly spelled queries. 30ms for typos wasn't something that we considered a problem and improving to ~5ms was really a side benefit of fixing things for the correct spellings.

Additional latency for actual typos seems ok, but degradation for correctly spelled queries felt really bad. The thing that was really damaging to the UX for us was when latency was spiking for search queries where it didn't need to.

Sure, but why does the title claim 300μs typo correction?

That's a good point, so we did a s/correct/detect/ on the title above. Thanks!

The title says 300μs typo detection.

How? If the query doesn't finish in 300μs, return error :)

Agreed. Confirming correct spellings is the basecase of the system and what the title is referring to, but that's not clear.

Also, 300µs _per word_, looking up a word in a corpus of 1.3M words. Not 300µs for correcting 1.3M words!

Reply on news.ycombinator.com