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

[JS] [Benchmarking] JavaScript microbenchmarks display regressions

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
performance

Research direction

Start by reviewing the benchmark restoration described in Apache Arrow issues/PRs 37657, 37668, and 38500, then compare the linked Conbench runs. Determine whether the JavaScript benchmark setup changed and whether that explains the regressions; done means documenting the cause or confirming that the performance changes need investigation.

Written by the indexing model from the issue text.

Description

Type: bug
Describe the bug, including details regarding any error messages, version, and platform.

I opened https://github.com/apache/arrow/issues/37657 a few months ago after noticing that the JavaScript microbenchmarks stopped working. Since then, @trxcllnt opened a PR https://github.com/apache/arrow/pull/37668 to fix them (which @assignUser merged in https://github.com/apache/arrow/pull/38500).

Now that they're running again, I noticed performance regressions in almost all of them. See the data in Conbench. Many of them are over 4x slower.

Is this expected due to a known change in the benchmarking setup? If so, I can annotate these performance jumps in Conbench so that future regression alerts are more effective. If not, someone more familiar with the JS codebase should probably investigate.

Component(s)

Benchmarking, JavaScript

Dominant language
TypeScript
Stars
112
Forks
23
Avg merge
17h 55m
Merged PRs (30d)
10

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 apache/arrow-js

All issues in apache/arrow-js

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.