Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about performance #3

Closed
MostHated opened this issue Mar 11, 2019 · 2 comments
Closed

Question about performance #3

MostHated opened this issue Mar 11, 2019 · 2 comments
Labels
question Further information is requested

Comments

@MostHated
Copy link

Hey there,
I am a big fan of your benchmark tests, I went to take a look to see if you happened to add this one in the mix but didn't see it. Did you ever get around to running your usual tests against this as well? I am interested to see how it stacks up against the usuals.

Thanks!
-MH

@nxrighthere
Copy link
Owner

nxrighthere commented Mar 11, 2019

Greetings. Asynchronous simulation within a single process is not possible at the moment because of this. The wrapper itself also has some places for optimizations using the latest C# features such as Span<T>, but I'm waiting until the first stable release will become available to avoid rewriting the code.

I am a big fan of your benchmark tests,

Glad to hear, thanks.

@nxrighthere nxrighthere added the question Further information is requested label Mar 11, 2019
@nxrighthere
Copy link
Owner

nxrighthere commented May 13, 2019

I've added support for direct access to native memory blocks of network messages using Span<T> in order to avoid marshaling, but this requires C# 7.2 and unsafe blocks.

To enable this functionality follow these steps:

  1. Define VALVESOCKETS_SPAN symbol.
  2. Define your message callback and use the appropriate function to receive messages.

If you are using the current more complex approach, you will need to refactor your code a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants