Hello everyone, I started adding convention plugin...

# gradle

[Vinícius Santos]

Hello everyone, I started adding convention plugins to a Android Project and the performance subject came up, does the convention plugins approach has is any significant impact in build time ?

[mbonnin]

https://github.com/gradle/gradle/issues/15886#issuecomment-1432923669

[mbonnin]

Welp nope, this is not the question you asked. Damn. 🤦‍♂️

[mbonnin]

Re: convention plugins, "it depends". If you previously were copy pasting your configuration code in all your build.gradle[.kts], then there might be some impact because both modules now depend on your build-logic

[mbonnin]

See also https://developer.squareup.com/blog/herding-elephants/

[mbonnin]

Overall, I like the flexibility and maintainability of convention plugins but it might be slower in some cases (not always)_._ If you find your build too slow, benchmark and fix regressions. The above blog post is a testament that convention plugins can be used efficiently in large projects

[tapchicoma]

Could you elaborate what performance issue do you see? 🤔

[Vinícius Santos]

By performance issues I mean a significant increase in build times.

[mbonnin]

Is that something you measured or something you're afraid of?

[Vinícius Santos]

Oh, I see, we used to rely on groovy closures to share build logic between our modules, but we saw the need for an alternative, since e have 100+ modules, and conventions plugins was our bet.
And since then our build times have raised, i don’t think convention plugins was the cause, but need a second opinion.

[mbonnin]

It depends a lot of factors so it's hard to give a definitive answer to this question. If you can, publish a build scan before/after the transition. If you can't then you'd have to investigate on your side. Enable remote build cache and configuration cache. Make sure your tasks are up-to-date, etc...

[Vinícius Santos]

Okay, I guess thats the only way to find out the cause, thank for the advice, and the info !!