10000 Feat/benchmark ci setup by Subh09 · Pull Request #19390 · webpack/webpack · GitHub
[go: up one dir, main page]
Skip to content

Feat/benchmark ci setup #19390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

Feat/benchmark ci setup #19390

wants to merge 3 commits into from
+136 −0

Conversation

Subh09
Copy link
@Subh09 Subh09 commented Apr 7, 2025

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

@linux-foundation-easycla Linux Foundation: EasyCLA
Copy link
linux-foundation-easycla bot commented Apr 7, 2025 •
edited
Loading

CLA Signed

The committers listed above are authorized under a signed CLA.

@Subh09
Copy link
Author
Subh09 commented Apr 7, 2025

What kind of change does this PR introduce?

This PR sets up the initial foundation for Webpack’s performance benchmarking system. It introduces:

A script to run benchmarks on various test cases and collect performance metrics (scripts/runBenchmarkCI.js)
A benchmarking helper using Benchmark.js to measure build times (test/helpers/runBenchmark.js)
A preliminary GitHub Actions workflow (.github/workflows/benchmark.yml) to enable CI-based benchmarking

This marks the beginning of a reliable benchmarking framework that will automatically track performance changes on every pull request—helping the Webpack team catch regressions early, gain performance insights, and support contributors with timely, data-driven feedback.

@Subh09
Copy link
Author
8000
Subh09 commented Apr 7, 2025

Did you add tests for your changes?

Not applicable. This pull request introduces benchmarking infrastructure and CI setup, which are tools for measuring performance rather than functional changes to Webpack itself. The benchmarking logic is validated through test runs on example cases, and further enhancements (like regression detection) will be added incrementally

@Subh09
Copy link
Author
Subh09 commented Apr 7, 2025

Does this PR introduce a breaking change?

No, this PR does not introduce any breaking changes. It adds standalone benchmarking scripts and a CI workflow that do not interfere with the core Webpack functionality or existing APIs.

@Subh09
Copy link
Author
Subh09 commented Apr 7, 2025

What needs to be documented once your changes are merged?

Once merged, the following should be documented:
How to run benchmarks locally using the scripts/runBenchmarkCI.js script.
Location and structure of benchmark test cases in test/benchmarkCases/.
CI workflow behavior, including how benchmark results are generated on each PR.
Instructions on interpreting the benchmark results JSON.
Future contributors can extend documentation for baseline comparison and result analysis once added.

@alexander-akait
Copy link
Member

Close in favor of #19692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Subh09 @alexander-akait
0