From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

:ok_hand: looks very nice :slightly_smiling_face:
I think someone asked you somewhere already, have you thought about measuring memory usage of processes spawned by Gradle? I tried a PoC a while back and it should be possible to modify jvmargs of each `JavaExec` task to attach an agent that would measure that process available memory and memory usage

It would be insanely helpful to understand how to optimize the build wrt max workers and understand why Gradle daemon disappears. The trickiest thing would be attaching to things like Kotlin compile daemon (or Gradle daemon itself)

Thanks <@UN48QB093>
Yes, it's already an open issue in the repository Github page
I will investigate it later soon.

ah, great :+1: I didn’t see it here: <https://github.com/janbarari/gradle-analytics-plugin/issues> am I looking in the wrong place?

Ops. I guess the issue has been removed
Can you create a new one?

Sure <https://github.com/janbarari/gradle-analytics-plugin/issues/51> not much details there but I haven’t exactly thought through what and how could be tracked :slightly_smiling_face: