Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Split benchmarks into warm and cold benchmarks

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

The issue does not name benchmark files or tests, so start by locating the benchmark definitions that exercise caching behavior. Separate measurements for first-run and repeated-call behavior, then run the affected benchmark suite and verify that warm and cold results are reported independently.

Written by the indexing model from the issue text.

Description

Some of the benchmarks are testing functions which behave differently on the first run because they cache data that they then use in repeated calls.

We should split the benchmark measuring such functions into warm and cold benchmarks. Otherwise the benchmarks have a large spread between the max value (cold run) and the min value and the mean becomes less meaningful.

Dominant language
Python
Stars
531
Forks
147
PR merge metrics
No merged PRs in 30d

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.

More from graphql-python/graphql-core

All issues in graphql-python/graphql-core

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.