[benchmark] Request for call-path / fairness review (GLD.SerializerBenchmark)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c
- Domain
- performance, tooling
Research direction
Start with the linked GLD.SerializerBenchmark wrapper, c/src/serializers/ser_tinycbor.c, and review its call pattern, options, encoder/decoder reuse, types, and buffer handling. Compare those choices with idiomatic performance-sensitive tinycbor usage; done means providing concrete fairness notes, a small wrapper PR if needed, or pointers for the benchmark course documentation.
Written by the indexing model from the issue text.
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: c, harness name: tinycbor).
Implementation we use:
https://github.com/leo-gan/GLD.SerializerBenchmark/blob/master/c/src/serializers/ser_tinycbor.c
We would value a short review of whether our measurement is fair and idiomatic:
- Does our call pattern match how you recommend using the library in performance-sensitive code?
- Should we change options, encoder/decoder reuse, types, or buffer handling?
- 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
- Dominant language
- C
- Stars
- 634
- Forks
- 222
- Avg merge
- 1d 25m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No 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 intel/tinycbor
-
CborValidateTagUse rejects valid tag 1 (epoch) with a floating-point value, and restricts tags 21-23 too muchPossibly taken @thiagomacieira claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Fixing CI/CDOpen
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kovidgoyal/kitty#10625 ·
Maintainers usually reply within 1 day
-
Feature Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
RubyMetric/chsrc#396 ·