3 ms·

I was wondering the same thing. They would have some writes indirectly due to searches, say if someone chooses to block a search result. They’re also going to

I was wondering the same thing. They would have some writes indirectly due to searches, say if someone chooses to block a search result. They’re also going to have some history and analytics surely. But yeah it’s not obvious what should cause per search write lock contention…

rwiggins 3y ago
You know, in retrospect, I think Kagi expects O(thousands) searches per month per user, so doing per-user usage accounting in the DB is fine -- thanks to row-level locking. Well, at least until you get a user who does 60k "in a short time period"... :-)
- bostik 3y ago
  It's the outliers and "surely nobody could be THAT awful" that kill you. Every time.
  - lanstin 3y ago
    I once had a stock alert product running on a backend I wrote. One person signed up for alerts for every single Nasdaq ticker there was. We didn’t expect that.