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

scaling mise with heavyweight configs #3773

Open
jdx opened this issue Dec 21, 2024 · 0 comments
Open

scaling mise with heavyweight configs #3773

jdx opened this issue Dec 21, 2024 · 0 comments

Comments

@jdx
Copy link
Owner

jdx commented Dec 21, 2024

are you using mise extensively? I'm talking 100+ tools, env vars, or tasks. That's far more than I benchmark mise with or ever use in my own testing. Given that, it's very likely mise has some bottlenecks that could be improved. While I could create a mock setup, I'm more curious what the real world performance looks like in actual configs people are using.

Some things that would be useful to know:

  • what does hyperfine "mise env" look like?
  • what does hyperfine "mise x -- echo" look like?
  • what is the overhead for running a simple "echo" task? (e.g.: hyperfine "mise run xxx")
  • are there other commands that seem to be lagging?

If there are obvious issues, like mise taking hundreds of ms to do any of the above, see if you can run mise with MISE_TIMINGS=1 and can see places it's getting hung up. You may not because I may need to add more traces.

With the fairly simple mise.toml in the mise repo most of these things run ~25ms right now. This is up a bit from a few weeks ago when it was down ~15ms. Unfortunate, but also not surprising since a lot of functionality has been introduced. <20ms is kind of my goal, however with a very large setup that's likely going to be quite difficult of course.

@jdx jdx pinned this issue Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant