Monitor how many UDP requests are aborted when the maximum number of concurrent requests is reached #830
Labels
- Admin -
Enjoyable to Install and Setup our Software
Enhancement / Feature Request
Something New
Needs Feedback
What dose the Community Think?
Optimization
Make it Faster
We handle a maximum of 50 UDP requests at the same time. When we have more than 50, we overwrite the latest one, and we give a second chance to the finish.
The demo server has been busy recently and I'm curious how many UDP requests we are discarding (not even replying).
By the way @da2ce7 we are using the
push_overwrite
method.That method overwrites the latest item, not the oldest. Does that make sense in our case? Would not be better if we overwrite the oldest request? That's the one that has had a longer time to be processed.
I'm planning to add a log (warning) before the
h.abort()
just to track the number of requests that are not processed. Then I can parse the logs to get the data like this.The text was updated successfully, but these errors were encountered: