You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I toyed around with some "load testing" (using the test CID URL from #124/#142), and found that:
ab -n 10000 -c 2 http://192.168.1.xxx:31080/ipfs/QmXjYBY478Cno4jzdCcPy4NcJYFrwHZ51xaCP8vUwN9MGm/
works great and has Failed requests: 0. But if I crank up the concurrency (the -c) just one notch from 2 to 3, it will soon fail with HTTP 429 = Too Many Requests (from Nginx), and have e.g. 996 Failed requests (for me).
Is this expected? Maybe it's totally fine, and exactly Working As Intended (WAI); I'm just wondering.
#143 COULD be related and relevant for this? If Nginx can't tell HTTP clients apart, will this happen IRL?
The text was updated successfully, but these errors were encountered:
I toyed around with some "load testing" (using the test CID URL from #124/#142), and found that:
works great and has
Failed requests: 0
. But if I crank up the concurrency (the-c
) just one notch from 2 to 3, it will soon fail with HTTP 429 = Too Many Requests (from Nginx), and have e.g. 996 Failed requests (for me).Is this expected? Maybe it's totally fine, and exactly Working As Intended (WAI); I'm just wondering.
#143 COULD be related and relevant for this? If Nginx can't tell HTTP clients apart, will this happen IRL?
The text was updated successfully, but these errors were encountered: