You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I want to profile my server but using run-tasks it doesn't have all the useful things as the live cpu/ram usage graphs. On the paper server they said to me that it's because the profiler is attached to the gradle task not to the server, I wanted to know if there was something I could do to show the graphs I never really used the profiler before so I'm maybe missing something, I still get a detailled report but only after stopping the server, and it doesnt allow to check for memory and cpu usage on the whole program.
The text was updated successfully, but these errors were encountered:
The run tasks extend the standard JavaExec task, from my understanding support would need to be added on the Gradle/IntelliJ side.
You might be able to run the task independently from IntelliJ and manually attach the profiler to the spawned JVM as a workaround. I haven't tried this though so won't be able to help with it.
IntelliJ/Gradle are already smart enough to attach to the correct JVM for debugging JavaExecs, so it seems worth checking for an issue/reporting that.
Hello, I want to profile my server but using run-tasks it doesn't have all the useful things as the live cpu/ram usage graphs. On the paper server they said to me that it's because the profiler is attached to the gradle task not to the server, I wanted to know if there was something I could do to show the graphs I never really used the profiler before so I'm maybe missing something, I still get a detailled report but only after stopping the server, and it doesnt allow to check for memory and cpu usage on the whole program.
The text was updated successfully, but these errors were encountered: