algolia / algolia/algoliasearch-client-csharp
Buffering
- Dominant language
- C#
- Stars
- 128
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
- Algolia Client Version: #.#.#
- Language Version:
### Description
I have seen that you use a lot of buffering (aka MemoryStream) for request and response parsing. It has some value for retries, but for the successful cases it causes unnecessary pressure on the GC.
Is this something you would accept a PR?
### Steps To Reproduce
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue concerns MemoryStream buffering during request and response parsing in the C# client. Start by locating those parsing paths and measuring allocation or GC pressure for successful requests, then determine how buffering can be reduced without losing the retry value described in the issue. Done means the approach is agreed and unnecessary successful-case buffering is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100