I have a performance problem in milestone-3 that doesn’t seem to be resolved in the latest milestone-5 snapshot. I understand that there are many performance improvements left to go for on the journey to milestone-5, 1.0-rc, and 1.0.
I have a project with ALOT of dependencies – Over 150 (that includes the transitive dependencies). On top of that, I have 5 maven repositories where they are getting pulled from. It seem that with every build, gradle continues to make HTTP HEAD requests for both the .pom and .jar file for these repositories. – Even when these files exist in the cache.
This is taking a long time to iterate over these dependencies and repositories.
I understand that work has been added in the new Wharf Local cache to manage the integrity of the cache, so perhaps that is why it has to continue to hit the respositories each time, but if so, is this optional, or configurable via a switch?
I could understand you might want to factor in build integrity for CI builds or official release builds, but as a developer trying to rapidly iterate on development, these hits are really dragging things down.
Can someone comment on whether this aspect of performance will indeed be fixed by 1.0, or even earlier? I’d be happy to share more detail on my build if it would help.