lspitzner / lspitzner/pqueue

Add benchmarks

Open
#48 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

performance testing
Dominant language
Haskell
Stars
17
Forks
12
PR merge metrics
No merged PRs in 30d

Description

I think I've picked off most of the low-hanging fruit, performance-wise. To make good decisions about smaller performance tweaks, we really need a benchmark suite. I would very much prefer to borrow someone else's, if there's a good one out there, but we can write our own if need be.

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

No files, tests, or entry points are named. Start by reviewing the repository and evaluating whether an external benchmark suite can be adopted before deciding whether to write one; done means a benchmark suite is available for comparing smaller performance tweaks.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.