Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A simple Solution to Multithreading the Querying.
Concept:
UdpClients Recieve Function is not Threadsafe, so it can only be one thread recieving.
The Send Function is fully threadsafe (according to its source) as it doesnt use any buffers.
So on each recieved Query a task is spun up to find the adress to that query and send it back via the UdpClient.
That creates a small overhead on each query, but allows to recieve further Queries while still working on one.
I used a small Benchmark (which is kinda finnicky to do without crashing somewhere on the socket) to determine an aprox speedup.
On my R9 5950X (32Threads, slight OC):
Old implementation: ~5k requests/sec
New Implementation: 7-8k requests/sec ~50% improvement
Requests were done on same PC using the Example project, woth this piece of code: