Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Use Buffer.MemoryCopy #544

Closed
Anderman opened this issue Dec 30, 2015 · 3 comments
Closed

Use Buffer.MemoryCopy #544

Anderman opened this issue Dec 30, 2015 · 3 comments
Milestone
Backlog

Comments

@Anderman
Copy link
Contributor

Buffer.BlockCopy has a large overhead for small size copy. This is because it has to find out a lot of things before it start copy see blockcopy.

MemoryCopy is almost a direct call to memmove see here
@muratg muratg added this to the Backlog milestone Jan 14, 2016
@benaadams
Copy link
Contributor

Situation may have changed dotnet/coreclr#3118

@cesarblum
Copy link
Contributor

Indeed. I don't think it's worth it making the switch to MemoryCopy. @halter73 what do you think?

@halter73
Copy link
Member

Yeah. This clearly seems fixed. If there is any evidence we should still switch, I'm open to reopening.

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

No branches or pull requests
5 participants
@halter73 @cesarblum @benaadams @muratg @Anderman