TASEmulators / TASEmulators/BizHawk
Use .NET 5's pinned object heap
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
https://tooslowexception.com/pinned-object-heap-in-net-5/
Can improve performance with certain interop scenarios. Do not mindlessly drop in this feature everywhere. Most things probably don't want it at all; better to do short term pins and keep things recompactable for lower fragmentation
edit: requires #1415 --yoshi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked pinned-object-heap article and issue #1415 first, then identify the specific interop scenarios where pinned allocations would improve performance without causing unnecessary fragmentation. Done should mean a narrowly scoped use of .NET 5's pinned object heap with evidence that it benefits those scenarios rather than being applied broadly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100