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
Remember stub files and their errors in result cache #5826
Comments
Some more context on this: about 15% of the time is actually spent to generate the Nette DI container for config.stubValidator.neon. Only 10% is actually analysing the files themselves (though still unnecessarily). Go figure. |
Maybe its related nette/di#269 |
Not sure. But one way or another, this extra 25% time can be avoided quite easily. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature request
While debugging #5825 , I'm discovering a range of interesting problems, mostly due to Windows' slow I/O.
I found it interesting that StubValidator doesn't use the result cache at all, because validating stubs takes nearly 25% of the pre-analysis step time (under xdebug that's about 1 second out of 4; at normal runtime it would be closer to 300ms).
This might seem insignificant, but I find it odd that stubs aren't remembered by the result cache like normal files.
I'm looking to save all the pre-analyse time I can find here, because this pre-analyse lag is a pretty huge annoyance for using PHPStan on Windows (particularly when integrated with PHPStorm, because it takes quite some time to respond - 300ms is a pretty significant amount of time in that case).
The text was updated successfully, but these errors were encountered: