https://github.com/cstickel/node-js-source-maps-performance-test

https://github.com/cstickel/node-js-source-maps-performance-test

Last synced: 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/cstickel/node-js-source-maps-performance-test
• Owner: cstickel
• Created: 2022-01-18T07:30:51.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2022-01-18T08:50:50.000Z (about 3 years ago)
• Last Synced: 2024-08-03T01:38:18.520Z (6 months ago)
• Language: TypeScript
• Size: 80.1 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-repositories - cstickel/node-js-source-maps-performance-test - (TypeScript)

README

        
# NodeJS Source Maps Performance Test

This is a minimal example to reproduce the issue

[--enable-source-maps is unnecessarily slow with large source files](https://github.com/nodejs/node/issues/41541)

in a close to real world scenario.

## Prerequisites

* [Node](https://nodejs.org/en/) Version v16.13.2 (should also work with any other version that has `--enable-source-maps`)

* [Yarn](https://classic.yarnpkg.com/lang/en/docs/install/)

## Steps to reproduce

* Run `yarn install`

* Run `yarn build`

* Run `yarn start-bundle`

* In a new terminal run `yarn artillery`

Instead of `yarn start-bundle` there are also `yarn start-without-source-maps`, `yarn start-unbundled`

and `yarn start-bundle-with-source-map-support`. Just run artillery against the different versions

to see the differences in performance.

Artillery is set to do 20 req/sec for 1 minute. This should show the effect, however for really fast machines

the `arrivalRate` of the load phase in `artillery.yaml` could be slightly increased.