mihaimaruseac:

This experiment could be repeated for other LLVM bumps (or TFRT ones too).


It think that all these bumps, with this cache miss rate, are going to impact also the disk-cache size o. disk as It could be quite common to have more then one branch/PR waiting for a review and so you need to switch forth and back between branches on different bumps (or probably need we to costantly rebase/merge when possibile?).
As we know clean up the disk-cache over time is really not a so straightforward task:

  

      github.com/bazelbuild/bazel
  

  
    
  
	  
  

  
    
      local caching: implement --disk_cache_size=GiB
    

    
      
        opened 
        
          
        
        May 2, 2018
      
      


      
        
          
          buchgr
        
      
    

    
        type: feature request
        P2
        team-Remote-Exec
    
  


  
    Break out from https://github.com/bazelbuild/bazel/issues/4870.

Bazel can use… a local directory as a remote cache via the `--disk_cache` flag.
We want it to also be able to automatically clean the cache after a size threshold
has been reached. It probably makes sense to clean based on least recently used
semantics.

@RNabel would you want to work on this?

@RNabel @davido