Skip to content
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

[Feature] Add Bun in benchmark #6559

Open
1 of 2 tasks
ImBIOS opened this issue Oct 18, 2024 · 2 comments
Open
1 of 2 tasks

[Feature] Add Bun in benchmark #6559

ImBIOS opened this issue Oct 18, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@ImBIOS
Copy link

ImBIOS commented Oct 18, 2024

  • I'd be willing to implement this feature (contributing guide)
  • This feature is important to have in this repository; a contrib plugin wouldn't do

Describe the user story

As a developer, I often want to know which PM is currently the W, but I often need to test it out locally each time we want to find out which one is the best compared to Bun.

Describe the solution you'd like

Add bun to benchmark

Describe the drawbacks of your solution

It might add the tension and energy of competition inside the yarn team between another package manager, but, it's good tension and energy to compete to be the best possible.

Describe alternatives you've considered

none

@ImBIOS ImBIOS added the enhancement New feature or request label Oct 18, 2024
@zkochan
Copy link
Contributor

zkochan commented Oct 18, 2024

Something to note, I was never able to reproduce locally the claimed perfomance of Bun (17x faster than pnpm and 33x faster than Yarn). Also, it wouldn't make sense to compare Bun with default configuration as they use offline cache by default. Which is an opt-in setting in all the current js-based node.js package managers.

@clemyan
Copy link
Member

clemyan commented Oct 18, 2024

I was never able to reproduce locally the claimed perfomance of Bun (17x faster than pnpm and 33x faster than Yarn).

Yeah, neither can we

offline cache by default. Which is an opt-in setting in all the current js-based node.js package managers.

Unless I'm mistaken about what you mean, Yarn's global cache is on by default. And, doesn't pnpm's store act as a cache?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants