rspack icon indicating copy to clipboard operation
rspack copied to clipboard

[Bug]: Regression from rspack v1.0.0-alpha.5 to v1.0.0-beta.0

Open pushkargupta9807 opened this issue 1 year ago • 23 comments

System Info

System: OS: Linux 6.5 Ubuntu 20.04.6 LTS (Focal Fossa) CPU: (32) x64 Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz Memory: 109.55 GB / 125.78 GB Container: Yes Shell: 5.0.17 - /bin/bash Binaries: Node: 20.11.0 - /usr/local/share/nvm/versions/node/v20.11.0/bin/node Yarn: 1.23.19 - /usr/bin/yarn npm: 10.2.4 - /usr/local/share/nvm/versions/node/v20.11.0/bin/npm Watchman: 20240317.093234.0 - /usr/local/bin/watchman Browsers: Chrome: 125.0.6422.76

Details

Hello, I am observing perf regression up to 50% when going from the rspack v1.0.0-alpha.5 to v1.0.0-beta.0 .

The application start times have gone from 40s to 50 sec and the recompile time for a typical scenario has gone up from 5.5 to 8.0 seconds.

It is surprising because as per the release notes for v1.0.0-beta.0 , there are expected perf improvements but I am observing regression. The only sigificant change I did with the new v1.0.0-beta.0 version was to absorb the breaking change with respect to the webpackDevServer5 .

Any one else experiencing any perf regression in development mode?

I had run into similar issue in the past and the cause was : https://github.com/web-infra-dev/rspack/issues/6743#issuecomment-2159753402

Thanks,

Reproduce link

No response

Reproduce Steps

start an application in serve mode with rspack v1.0.0-beta.0 make a GUI change and observe the regression in recompile times when compared with previous rspack v1.0.0-alpha.5

pushkargupta9807 avatar Sep 04 '24 02:09 pushkargupta9807