Skip to content

Memory Thrashing #361

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.

Sign up for GitHub

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

Jump to bottom
Closed
YulerB opened this issue Oct 5, 2017 · 3 comments
Closed

Memory Thrashing #361

YulerB opened this issue Oct 5, 2017 · 3 comments

Comments

@YulerB
Copy link
Contributor

YulerB commented Oct 5, 2017

Allot of memory is allocated and destroyed of different byte lengths.
This has impact on the CPU and on memory fragmentation, leading to higher latency.
I have 2 recomendations,

  1. use socket methods using SocketAsyncEventArgs
  2. pool the byte[] that are being allocated.
@YulerB
Copy link
Contributor Author

YulerB commented Oct 5, 2017

This ties in with issue #303, as ArraySegment may be part of the solution.

@YulerB YulerB closed this as completed Oct 16, 2017
@lechu445
Copy link
Contributor

lechu445 commented Apr 17, 2018 •
edited
Loading

@YulerB Why this issue was closed?

@lukebakken
Copy link
Collaborator

#706 may address this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lukebakken @lechu445 @YulerB