-
Notifications
You must be signed in to change notification settings - Fork 993
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
[RFC]: CLI Speed Improvement #6027
Comments
In addition to the speed, I want to bring up the problem with the Prompt Windows. Why does redwoodjs's CLI raise so many Prompt Windows which only stay for a little while. Can we simply disable this? |
@peterp Interesting! May we know how did you make this graph? |
Thx for letting me know! |
@TristanWYL That's
|
Awesome! Thanks so much |
Even though #6028 was merged, I'll reopen this as we plan on making more improvements. |
I just had a idea to improve performance What if we create CLI as standalone built with Non Javascript Language For Example vlang ( Fastest programming language ) |
Summary
The CLI is a bit slow. It takes ~1150ms to run
redwood --help
. I believe speed is part of DX and we should aim for ~300ms response time in the CLI.Detailed proposal
We're also using yargs at Snaplet and the approach we've taken is to separate the handlers (the logic that the CLI runs) from the structure that the CLI runs. We do this by asynchronously importing the code from the handler.
But first, let's figure out what makes the CLI slow:
Normal:
1.143 s
Removing all the commands:
686.5 ms
Removing all the middleware:
119.8 ms
So with these results we can see that middleware adds an additional 500 ms (Surprizing!), and all the commands add another 600 ms.
[As I'm working on this I'll update the issue with additional information]
Are you interested in working on this?
The text was updated successfully, but these errors were encountered: