Consider shipping a managed allocator
Maintainers usually reply within 1 day
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
The issue names no files, tests, or entry points. Start by locating the existing allocator and buffer-allocation paths in the C# implementation, then investigate 64-byte alignment, small allocations, and the impact on the LOH. Done requires a measured decision on whether a managed allocator is viable without violating applicable use cases.
Written by the indexing model from the issue text.
Description
Describe the enhancement requested
A managed allocator would not conform to the Arrow specification in that its buffers wouldn't be 64-byte aligned. But in e.g. a purely-managed service environment where the buffers are being assembled to ship out on a wire, the alignment shouldn't really matter and the managed allocator might be substantially faster, at least for small allocations. (Impact on LOH would need to be understood.)
- Dominant language
- C#
- Stars
- 41
- Forks
- 31
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from apache/arrow-dotnet
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
apache/arrow-dotnet#410 · 4 comments ·
Maintainers usually reply within 1 day
-
ArrowArrayConcatenator: null arrays are refused, and dictionary arrays lose their dictionaryPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
apache/arrow-dotnet#446 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
apache/arrow-dotnet#409 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/arrow-dotnet#397 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/arrow-dotnet#378 ·
Maintainers usually reply within 1 day
All issues in apache/arrow-dotnet
Similar issues
-
bug
Difficulty 2/5 Half a day Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PCL-Community/PCL-CE#3652 ·
Maintainers usually reply within 1 day
-
agentic-workflows Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MCP error results with only structuredContent lose their payloadPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
anthropics/anthropic-sdk-csharp#286 ·
Maintainers usually reply within 1 day
-
area:frontend bug FE P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
klasolsson81/jobbliggaren#2010 ·
Maintainers usually reply within 1 day