You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
hyperfine "mise env"
look like?hyperfine "mise x -- echo"
look like?hyperfine "mise run xxx"
)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.The text was updated successfully, but these errors were encountered: