It’s the former, it took 22 secs to check the remote and return. It’s a long time but there could be multiple causes behind this (network ? Gradle slowness in this particular build, etc. It does not necessarily mean that the contacted remote build cache was itself slow)
thank you 1
😮 1
François Guillot
10/12/2022, 6:44 AM
Is this always happening? You could find out by inspecting this particular metric on the performance dashboard (Build cache overhead / Downloading, which contains remote cache hit and misses overhead). Then we’ll need to look at those builds to try to get why it’s happening
p
Paul Blundell
10/17/2022, 6:41 PM
You mean like this?
f
François Guillot
10/17/2022, 6:47 PM
Yes. That's across the whole set of builds, or for the given build in the 'tooltip' you have for a particular build in the set. If that's bigger than expected, I suggest to create a support ticket with a support bundle and the scan dump of the problematic build scan(s)