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

Benchmark with memory allocations

Open
#104 3 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
ruby
Domain
performance, tooling

Research direction

Start by comparing benchmark-ips with the linked benchmark-ipsa project, focusing on how it accesses the job object and call list. The work is done when benchmark-ips reports memory allocations alongside iteration statistics without affecting the original benchmark session's performance.

Written by the indexing model from the issue text.

Description

Hi all,
I've made a version of benchmark-ips that also shows memory allocations: https://github.com/jondot/benchmark-ipsa

It extends benchmark-ips by hijacking the job object and getting the call list. It does not have any performance implication over the original test session.

This is one step closer to the go bench tool which allows you to embed allocation info in addition to the iterations stats.

Dominant language
Ruby
Stars
5.7k
Forks
370
No merged PRs in 30d

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 fastruby/fast-ruby

All issues in fastruby/fast-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.