Project with cascading files benchmarks - compare effect on signature files on incremental build #14136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This set of benchmarks validates that the existence of .fsi files does have multi-fold impact on the speed of incremental build.
That is, especially if the file being modified happens to be between beginning and middle of the project.
The benchmark was running in 2^3= configurations corresponding to arguments of FsCheck, and the fact whether .fsi files were added to the compilation or not.
enablePartialTypeChecking = this.PartialCheck,
enableParallelCheckingWithSignatureFiles = this.ParaChecking
If you focus on a specific example, let's say **ParseProjectWithChangingMiddleFile ** which changes the middle file of a 128-files large project, you can see the differences across these 3 boolean configs.
In this case, the impact on the speed of incremental build can be up to 2-3x in terms of speed gains.