Test de charge FAILED : where could this come from ?

[MichaelBitard]

• RAM trop faible ? => probably not because the docker logs show answers are handled, but some in more than 30sec
• timeout NGINX ?
• timeout FAST API / gunicorn (timeout 180) => a probably not
• timeout ES ?
• timeout Netlify ? => probaly not
• timeout DNS etalab ? => probaly not
• chrome (browser) stackoverflow

Sounds like a timout of 10seconds. In the logs I see some calls answering in more that 10 seconds, so it could be linked to NGINX of FASTAPI

link deepset-ai/haystack#1228

[MichaelBitard]

First hint: the RequestLimiter in haystack seems to responds 503 errors with "The server is busy processing requests."

Step to reproduce:
I launched 4 parallel curl with tmux: https://asciinema.org/a/Ov6d1NmzTzv6tPRXcKInm6pcS

I found a hardcoded value of 4 parallel requests:

concurrency_limiter = RequestLimiter(4) in haystack/rest_api/controller/search.py

[guillim]

created this issue in Haystack : deepset-ai/haystack#1229