Creating benchmarks to showcase speed and improvement over time

Open
#183 13 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points. Start by getting maintainer guidance on which ImageSharp features and environments should be benchmarked, then review the relevant implementation areas. Done means an agreed benchmark setup that measures performance across the chosen hardware or environments and can show changes over time.

Written by the indexing model from the issue text.

Description

chore
Description

Attempting to start discussion around benchmarking performance for various features across different environments/hardware. I see this as an easy way to deter naysayers, communicate performance improvements/progress, highlight areas in the need of the most optimization, etc.

I'd be happy to get something started, but was hoping for a minimal amount of guidance/direction before diving in so that an eventual PR has a higher chance of being pulled in.

Dominant language
C#
Stars
8k
Forks
899
Avg merge
1d 5h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

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 SixLabors/ImageSharp

All issues in SixLabors/ImageSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.