We get emails showing that we exceed our max QPS.
Algolia searches in most cases from the very first button pressed. That means that only typing a search word into the search input launches several queries. All of your lower level clients have to program some sort of debounce, or time-delay, into their search fields, because, at least on the free tier, 30 QPS (and 75 QPS on the essential plan) is just too low. I’d really really love to use Algolia.
If we’d launch the site with algolia and, as is standard in your wordpress plugin, used search from first button pressed, our visitors would quickly overwhelm the 75 max QPS. Would you bill us extra? Would the service just stop(as you mention in the email notifications)?
Is there perhaps another reason that we get a very high QPS, even though we are only two developers on the project? is there some optimization that we should do within the Wordpress?
Debounce is achievable with the queryhook parameter. Wordpress plugin outofthebox does not set any debounce time.