bench: memory and GC pressure, and dinero.js's bigint calculator

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active

Research direction

Start with docs/reference/limitations.md and inspect the existing speed benchmark and benchmark battery under compare/bench to find where dinero.js 2's bigint calculator belongs. Measure allocations, heap use, and GC per operation for ducat and the money libraries, then render a comparison table. Treat the clean-machine numbers as pending the next Genoa run; done means the benchmark includes the bigint calculator and the memory results are shown without new README claims.

Written by the indexing model from the issue text.

Description

area: tests

From docs/reference/limitations.md (Alex, 2026-11-13: worth doing soon).

  • measure allocations, heap and GC per operation for ducat and the money libraries in compare/bench (Node's --expose-gc and process.memoryUsage, or performance.measureUserAgentSpecificMemory where available), and render a table
  • add dinero.js 2's bigint calculator to the speed benchmark (it's already in the battery)
  • the clean-machine numbers come from the next Genoa run; no README claims until then
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
35m
Merged PRs (30d)
242

Getting set up

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 public/ducat

All issues in public/ducat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.