Cysharp / Cysharp/MemoryPack

[benchmark] Request for call-path / fairness review (GLD.SerializerBenchmark)

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

Nobody has claimed this yet.

Dominant language
C#
Stars
4.7k
Forks
313
PR merge metrics
No merged PRs in 30d

Description

Hello,

I'm Leonid Ganeline. We maintain an open multi-language serializer benchmark:

https://github.com/leo-gan/GLD.SerializerBenchmark

Your library is included in the suite (language: csharp, harness name: MemoryPack).
Implementation we use:

https://github.com/leo-gan/GLD.SerializerBenchmark/blob/master/c-sharp/src/Serializers/MemoryPackSerializerSer.cs

We would value a short review of whether our measurement is fair and idiomatic:

  1. Does our call pattern match how you recommend using the library in performance-sensitive code?
  2. Should we change options, encoder/decoder reuse, types, or buffer handling?
  3. Is there a better API (or a second entry point worth a separate row in the suite)?

Concrete notes or a small PR against that wrapper would help a lot. We are happy to credit you in the docs.

The repo also includes a short Serialization course (101–401). If something important about your design is easy to misstate, a pointer is welcome—we can update the docs ourselves.

Thank you for maintaining this library.

Best regards,
Leonid Ganeline

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.

Research direction

Start with the benchmark wrapper at c-sharp/src/Serializers/MemoryPackSerializerSer.cs and compare its call pattern, options, reuse, types, and buffer handling with MemoryPack's documented usage. Done means providing concrete fairness feedback, identifying any needed API or wrapper changes, and optionally preparing a small PR against the benchmark repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
performance, testing
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.