We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
https://github.com/expressjs/express
I deployed a basic express app (hello world) using tsx and noticed CPU spikes. I then deployed the same app with ts-node and the spikes went away.
I then built a docker image and ran a benchmark with wrk: wrk -t12 -c400 -d30s http://localhost:3000/api
wrk -t12 -c400 -d30s http://localhost:3000/api
I had the following benchmark utils setup in the /api endpoint:
/api
console.log(process.memoryUsage()); for (const [key, value] of Object.entries(process.memoryUsage())) { console.log(`Memory usage by ${key}, ${value / 1000000}MB `); } console.log(process.cpuUsage());
I expected tsx to perform better than ts-node. But as you can see from the screenshots below, it unfortunately does not.
In my tests tsx is consuming 3x the CPU.
I'm very interested in using tsx and hope this is something that can be reasolved.
ts-node
tsx
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Acknowledgements
Minimal reproduction URL
https://github.com/expressjs/express
Problem & expected behavior (under 200 words)
I deployed a basic express app (hello world) using tsx and noticed CPU spikes. I then deployed the same app with ts-node and the spikes went away.
I then built a docker image and ran a benchmark with wrk:
wrk -t12 -c400 -d30s http://localhost:3000/api
I had the following benchmark utils setup in the
/api
endpoint:I expected tsx to perform better than ts-node. But as you can see from the screenshots below, it unfortunately does not.
In my tests tsx is consuming 3x the CPU.
I'm very interested in using tsx and hope this is something that can be reasolved.
ts-node
tsx
Bugs are expected to be fixed by those affected by it
Compensating engineering work will speed up resolution and support the project
The text was updated successfully, but these errors were encountered: