Find TooManyRequets

Andrey Gushchin

Vote:

Hi All,
We have a serious trouble with find service in production.
We have a license which limits us with 100 requests per second to the search Index.

But we are experiencing very high load and constantly crossing the limit.

Does anybody have an expirience with how to deal with such limit if
users triggers more search requests per second than the limit allows?

#89438

Aug 16, 2014 14:05

Per Magne Skuseth

Vote:

100 requests per second is quite a lot. Do you generate lists or such using Find on pages that are often loaded? I would suggest that you utilize Find's .StaticiallyCacheFor(..) as much as possible.

http://world.episerver.com/Documentation/Items/Developers-Guide/EPiServer-Find/8/DotNET-Client-API/Searching/Caching/

#89439

Aug 16, 2014 17:11

Andrey Gushchin

Vote:

Thank you!

Yes, you right. We are using Find results on the most popular pages (Home page among of them).

And we have not thought about the limits until high load came to the site.

Now we are caching partials with find results on the pages and started to cache most of the find requets.

But it is still very interesting how Find wants developers to not cross the license limit?
How to control this efficiently to not get the TooManyRequests?

#89440

Aug 16, 2014 19:14

Try our conversational search powered by Generative AI!

Find TooManyRequets