-
-
Notifications
You must be signed in to change notification settings - Fork 615
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
monitoring type-check performance on CI #3377
Comments
Hi @m-shaka I also wanted that! First, we must create the benchmark method to measure the type-check performance. I've used this way ago: https://github.com/microsoft/TypeScript/wiki/Performance#performance-tracing It will be good to make some script to show the score as a concrete number: like |
found that --diagnostics option of
I'll make POC later |
Yeah, that's useful when you're looking for the bottleneck in compilation But the first thing we need is to be able to notice the possibility that type checking performance has declined, isn't it?
|
Yes. Exactly. We have first to measure the performance. |
What is the feature you are proposing?
Some changes may accidentally damage type-check performance like #3074 (comment)
It would be great if you could know if your change has an impact on type-check performance.
What do you guys think? Please tell me your opinion and possible solutions to this.
A minimum solution that came to me is storing the result of type-check profiling on
main
branch and comparing it with the one of the PRThe text was updated successfully, but these errors were encountered: