Ask HN: How can Kagi be so fast and customizable?
Each customization I do to Kagi means the next search query has to be totally different. That might mean the UI also has to change to add/remove things that certainly require an index/DB search.
And yet, I always get sub 200ms first-byte responses.
How is that even possible? Is that edge computing? How would you architect such a thing?
15 comments
[ 3.7 ms ] story [ 46.2 ms ] threadTake the standard, $5 plan. It gives you 300 searches PER MONTH. That’s 10 per day. I’m sure most of us do 10 searches within minutes while working.
Still, getting a single, customized, full web search done in 200ms is impressive: scaling that to more requests is easier today with scale-out (for this particular problem type, which is basically read only) than getting that single search to perform.
I can't picture anyone willing to spend any money for better search quality consciously adjusting their personal search behavior because of the price difference in Kagi tiers per number of searches.
In other words, these quantity limits don't change behavior, other than abusive/exploitative behavior (e.g. account sharing, bots, etc.).
Instead, I would guess just the "free vs. fee" discriminator cuts enough users it enables not having to serve an infinitely long tail of freeloaders with a lowest common denominator SERP.
I bet you're overestimating your search volume. (I know I did when I first subscribed -- I was nervous I'd hit the limit in a day.)
Your singular case does not really prove much: maybe you are just in the same area their DC is?
Still, a full, customized web search result in 200ms (though, first byte is not really indicative of that) would be impressive.