Build Profiling

Performing a performance analysis can help you identify performance bottlenecks in your project, allowing for targeted optimization.

Using Rsdoctor

Rsdoctor is a build analyser that can visually display the compilation time of each loaders and plugins.

Please refer to Use Rsdoctor for more information.

Node.js Profiling

In general, the performance overhead on the JS side will be greater than that on the Rust side, and you can use Node.js profiling to analyze the overhead on the JS side.

Run the following command in the project root:

# dev
node --cpu-prof ./node_modules/@rsbuild/core/bin/rsbuild.js dev

# build
node --cpu-prof ./node_modules/@rsbuild/core/bin/rsbuild.js build

The above commands will generate a cpuprofile file. We can use speedscope to visualize this file:

# Install speedscope
npm install -g speedscope

# View cpuprofile content
# Replace the name with the local file name

Rspack Profiling

Rsbuild supports the use of the RSPACK_PROFILE environment variable for Rspack build performance profile.

# dev

# build
RSPACK_PROFILE=ALL rsbuild build

This command will generate a rspack-profile-${timestamp} folder in the dist folder, and it will contain logging.json, trace.json and jscpuprofile.json files:

  • trace.json: The time spent on each phase of the Rust side is recorded at a granular level using tracing and can be viewed using
  • jscpuprofile.json: The time spent at each stage on the JavaScript side is recorded at a granular level using Node.js inspector and can be viewed using
  • logging.json: Includes some logging information that keeps a coarse-grained record of how long each phase of the build took. (Not supported in development environment yet)

For more information about Rspack build performance analysis usage, please refer to Rspack - Profiling.