Web server performance degradation in recent releases
Posted: Thu Apr 02, 2020 3:41 am
Hi all,
Not sure if anyone has experienced this or has any clue if there is anything I can change on my side but since a recent update, couple weeks back (don't remember the version number, but I know it's the one that stated "Redesigned web server socket code (performance and reliability)"), I have noticed that using the endpoint that fetches static images (JPEGs) from live feeds now is not as smooth as before.
The endpoint I'm referring to is -> %bi-hostname%/image/%camera-name%/
The endpoint still works as expected, but once in a while takes several hundred milliseconds more than before, and I no longer can make multiple calls to the same endpoint (same endpoint but different cameras) at the same time. My use case is that every 1 second I call that same endpoint, but changing the %camera-name% for around 10 different cameras. In the past that used to work really well, getting all JPEGs in around ~50ms each (well, all at the same time), now it's not uncommon that one our couple of those requests go to 300+ms while the rest are still around the 50ms mark.
Is anyone aware if there is any sort of rate limiting recently added to the web server? If so, is there is any setting to disable it?
Thanks!
Not sure if anyone has experienced this or has any clue if there is anything I can change on my side but since a recent update, couple weeks back (don't remember the version number, but I know it's the one that stated "Redesigned web server socket code (performance and reliability)"), I have noticed that using the endpoint that fetches static images (JPEGs) from live feeds now is not as smooth as before.
The endpoint I'm referring to is -> %bi-hostname%/image/%camera-name%/
The endpoint still works as expected, but once in a while takes several hundred milliseconds more than before, and I no longer can make multiple calls to the same endpoint (same endpoint but different cameras) at the same time. My use case is that every 1 second I call that same endpoint, but changing the %camera-name% for around 10 different cameras. In the past that used to work really well, getting all JPEGs in around ~50ms each (well, all at the same time), now it's not uncommon that one our couple of those requests go to 300+ms while the rest are still around the 50ms mark.
Is anyone aware if there is any sort of rate limiting recently added to the web server? If so, is there is any setting to disable it?
Thanks!