NetQueue concurrency #156
Comments
|
As far as I remember it was for performance; ConcurrentQueue was expensive, esp. when uncontested. It was a very long time ago tho; no idea if this is the case today. |
|
Thanks for the info. Very helpful!
…On Fri, Dec 2, 2022, 11:48 Michael Lidgren ***@***.***> wrote:
As far as I remember it was for performance; ConcurrentQueue was
expensive, esp. when uncontested. It was a very long time ago tho; no idea
if this is the case today.
—
Reply to this email directly, view it on GitHub
<#156 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHRCJ3C2WD76CUQCJCC723WLIY7RANCNFSM6AAAAAASSBROPA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why wouldn't you have used
ConcurrentQueue<T>instead of rolling your own (NetQueue<T>)? Asking as I am studying the code base for a deeper understanding of the client/server topography in games.The text was updated successfully, but these errors were encountered: