If I disable IB and re-run I get cache hits. If I re-enable it, I think I see myself getting misses and I presume it's based on developer machines handling the distributed request, and their filesystem not being the same.
I hoped the IB 'containerization' method xoreax uses would shield from this issue.
If this is not the case - and I maybe have IB set up wrong somehow, please let me know.
Otherwise I will draft this (filesystem congruence for machines with distributed seating) into our project requirements per stashed's requirements.
Hi. I am testing stashed. I think cache hit is not very good. I did number of rebuild and clear cycles with stashed. Also increased disk cache size. Before the last rebuild I cleared logs, and statistics. Then I get in statistics:
Job hits: 1940
Job miss: 2
Blob hit: 10,531
Blob miss: 2,146
In logs, I get 340 warnings of the same type having reason: "/out:something\foo.rc.res.dep.obj", that appear to be related to compilation of resources.
Q1: how can I diagnose where are blob misses coming from?
Q2: is it possible to disable temporarily stashed to have more builds without it?
If stashed was to learn how to cache with #import and if pch is used then I suppose the easiest a workaround is to put the #import directives in the StdAfx.h and the other files could simply include the generated tlh files instead of using #import.
Since the pch has to be compiled before everything else, even when compiling in parallel, the tlh and tli files will be generated once only and can be used by the other compile units.