This message was deleted.
# caching
s
This message was deleted.
n
Storing results in a build cache is not free. This is expected to make certain builds slower. A build scan will show you more information of where the time is spent. That being said if the time difference is quite significant then that is not expected.
c
Nope. It's just marginal. Interesting! I would have thought the cache wasn't free in the realm of space, but i would have thought that it always made builds faster. I guess that's what gradle-doctor doesn't outright recommend it? 😅 I just noticed the same thing when overnight I benchmarked parallel builds. To answer your question though. clean builds were like 6x faster with caching. but incremental builds were like a second slower. so I think we will end up leaving it enabled.
l
We are planning some improvements that are expected to reduce the overhead of storing stuff in the cache that will likely help here as well.
🙌 6
c
@lptr since I'm going to ship this sorta soon. are these improvements like right around the corner (1 day to a week) or are you just giving me a general heads up that in a few months this should also be improved?
l
No, these are months in the future at best.
💯 1
c
thank you. appreciate it