Consider using an arena allocator

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
performance

Research direction

Read the issue and the linked arenas.md document to understand the proposed arena allocator and how it might apply to SimdJsonSharp. Then inspect the repository's current allocation approach and define whether an arena-based implementation is appropriate; done should include a documented design decision or a working implementation with evidence of its impact.

Written by the indexing model from the issue text.

Description

Just a thought...
I could imagine an arena allocator doing quite well in this kind of use case.
@mgravell introduced a C# implementation here:
https://github.com/mgravell/Pipelines.Sockets.Unofficial/blob/master/docs/arenas.md

Dominant language
C#
Stars
687
Forks
48
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EgorBo/SimdJsonSharp

All issues in EgorBo/SimdJsonSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.