NightOwl888 commented on PR #1172: URL: https://github.com/apache/lucenenet/pull/1172#issuecomment-3263790846
The config is too complex to go through everything, but here is a representative of the difference between a cache hit and cache miss comparing apples to apples (same project, same os, same platform, same target framework). In this case, we shaved nearly 2 minutes off of the runtime. ### Cache Miss <img width="714" height="669" alt="image" src="https://github.com/user-attachments/assets/3794ac88-7668-48a0-bfcd-e0b0673a8609"; /> ### Cache Hit <img width="713" height="654" alt="image" src="https://github.com/user-attachments/assets/14713699-d8ba-4c82-9dd3-ac7d29ea7da9"; /> As you can see above, the run time for build is ~35s, so we may be able to shave another 15-20s if we enable incremental build caching, although I am not sure whether that will offset the extra amount of time downloading the cache will take. Not sure it is worth the complexity. I went to find the worst case I could think of (OpenNLP) and it still only takes about 1 minute to build. The below is also a cache miss, so the runtime is still fairly short (due to the simple tests). We gain a lot by building each project on a separate job here on GitHub Actions. However, on Azure DevOps it will probably be worth it to do both types of caching, since the build takes a significant amount of time when the solution is built all at once. <img width="712" height="668" alt="image" src="https://github.com/user-attachments/assets/ac932c32-67bf-40c3-8270-6314ed673c18"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
