Cache Hit

Gradle creates a cache for the executed task to be reused in the next incremental builds, the more cached tasks lead to faster builds.

It represents the project and modules tasks average cache hit rate (tasks run with FROM_CACHE or UP_TO_DATE).

Higher is better

%table-data% %overall-diff-rate%

#	Module	Hit	Diff Rate
Overall		%overall-cache-hit%

Best and Worst
(Green is best)

Hit represents the cache usage of executed tasks within a module.
Diff Rate shows the improvement in cache usage between the first and last execution over the report period.
Best and Worst represents the module's most and least cache usage.