This autocomplete suggests domains that don't exist. You can just type garbage and it will suggest something, but then if you go there, there are no records.

It seems like one purpose of an autocomplete box is help you avoid typos, so that makes it less useful.

If you’d like to reduce the network latency further you can store each trie node as a file, naming it conveniently the prefix path to that node. Then dump the few hundred million files onto R2.

Now the traversal can be done completely via CDN lookups!

Unfortunately this approach doesn't feel that great down here in Australia, definitely a function of latency.

I think you could get a lot closer by framing this as an optimization problem, where you use the full alphabet dictionary, but add a residual prediction which aims to cover as much of the remaining domain name tree as possible weighted by popularity. This tree could then be pre-baked and stored with the same system. This would probably get you p99 0ms even in Australia.

Pretty sure we mean < 1ms rather than actually instantaneous.

Looks more like 500ms?

Autocomplete aside, this is a pretty nifty tool.

its pretty clever but what happns when someone pastes a domain or uses IME or voice input? the api being that fast is still impressive.

Clever but that’s not how we measure latency.

KeyDown events don’t work great for mobile, though.

[flagged]