Add build operation signals to YourKit snapshots about gradle-profiler HOT 9 CLOSED

It doesn't profile warmups, you only get telemetry for warmups. That's normal, both Yourkit and JProfiler collect telemetry as soon as they are loaded. The actual CPU and memory hotspots are only from the profiled run.

@ingokegel is there some way to get a snapshot that starts at the moment the recording was started instead of when the agent was loaded?

from gradle-profiler.

Adding

invoke("startVMTelemetryRecording");

to JProfilerController.startNow() would clear the previous telemetry data. I'm not sure if that improves anything, though. The bookmarks in the telemetry views already show where the recording has started. Also, clearing the telemetry would not reset the time origin of the snapshot (this is currently not possible).

from gradle-profiler.

Thanks Ingo. The same is true for YourKit, so nothing we can change from the Gradle Profiler side.

from gradle-profiler.

Ah, I was meaning to ask about bookmarks - that certainly does the trick. By bookmarks do you mean the message events? I see the CPU sampling started/stopped event. Would it make sense to add other useful events from the chrome trace, like tasks starting?

from gradle-profiler.

That would only work when using method instrumentation, which adds a lot of overhead and skews the results. That being said, there is an open issue to support YourKit probes (#23), which would probably allow you to get this kind of more detailed info.

from gradle-profiler.

Why would you need method instrumentation though? Can't you use the same signals the chrome trace output is using? I generated both outputs in a single run of gradle-profiler, so I expected the traces in the chrome trace could just be added to the YourKit snapshot.

from gradle-profiler.

Oh I get it now, you'd inject logic that talks to the yourkit agent. Makes sense. Would you be interested to to look into this?

from gradle-profiler.

from gradle-profiler.

Closing since there was no more development here.

from gradle-profiler.