-
Notifications
You must be signed in to change notification settings - Fork 62
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.
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
nx is slower than turbo (windows machine) July 16 #7
Comments
Hey @bryantobing12! Your results definitely show that, I'm not sure what the reason would be for you. I just reran the benchmark on my windows PC. Lerna / Lage both had some issues with my setup, but here were the numbers for turbo and Nx:
|
Running the benchmark I get similar results saying that NX is slower than Turbo and Lage. This is on Arch Linux btw, on the 13/06/2023. The command ran in 672ms
------------------------
results
------------------------
average lage time is: 672.4
average turbo time is: 431.1
average nx time is: 713.4
nx is 0.9425287356321839x faster than lage
nx is 0.6042893187552566x faster than turbo This shows that Turbo is 1.654 times faster than NX and 1.559 times faster than Lage.
System:
OS: Linux 6.3 undefined
CPU: (32) x64 AMD Ryzen 9 7950X 16-Core Processor
Memory: 17.92 GB / 30.49 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 20.3.0 - /usr/bin/node
npm: 8.19.2 - /usr/bin/npm |
Not sure I read this correctly but this is my results by running
npm run benchmark
I ran this twice and got similar results
npx envinfo
The text was updated successfully, but these errors were encountered: