Starting with profiling. any good suggestions for books
I am trying to understand software profiling from a theoretical perspective. Any suggestions for books/articles/video lectures are appreciated.
20 Replies
⌛ This post has been reserved for your question.
Hey @lars! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./closeor theClose Postbutton above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 300 minutes of inactivity.
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.I don't have a book or article or similar but essentially, there are different things that are possible:
- ~CPU:
- Sampling: Every <duration, e.g. 100ms>, you create a thread dump to have and take a look at which methods commonly appear in the thead dumps
- CPU profiling: You can use a tool like
perf (A Linux tool which integrates with the OS) which tells you what takes CPU time or similar.
- time-based profiling: You add an agent that modify the code of the classes/methods you want to profile. So essentially it measures the time for the relevant methods take
- You can also measure allocations (use an agent that adds code for all allocations)
- JFR can fire events when certain things happen (e.g. file accesses)
- GC logs: The GC logs a lot of things but this is disabled by default. You can enable it and view the logs or use a tool that extracts information from itThere's a 3h playlist for async-profiler but I think that's mainly about using it: https://www.youtube.com/playlist?list=PLNCLTEx3B8h4Yo_WvKWdLvI9mj1XpTKBr
are these profiling tools independent of the language that we use?
Most Java profiling tools like async-profiler, JFR (that does the event thing), VisualVM, GC logs etc are Java-specific
perf is a Linux tool which is also used by things like async-profiler
so perf is not language dependent
https://www.youtube.com/watch?v=Cw4nN5L-2vU
Andrei shared this in his x account. should I watch this first.
Devoxx
YouTube
Taming performance issues into the wild: a practical guide to JVM p...
The session will start with a quick introduction to the theory of profiling discussing the motivations, explaining the different types of profiling and visualization format while listing the tools available for this purpose. This also includes some tooling for reliably emulating the load generation and validating the improvements.
Then we will g...
the thing is that Java (specifically the JVM) has many capabilities that aren't really available for other languages
and there's a lot of tooling for Java/JVM languages, especially in this area
Devoxx talks are typically pretty good
but other languages must also have similar tools for profiling them. right?
For JVM languages (Kotlin, Scala, Groovy, Clojure and maybe I also forgot some), you can use the tools I mentioned. While there are other tools that are not language-specific, these have fewer capabilities and there are less tools. And I don't think there are many language-specific tools for other languages
For the first part about JVM languages: The tools I mentioned are not really language-specific but platform-specific (made for the JVM)
I mainly use java. but wanted to learn generic tools so that if I shift to some other lang I dont have to learn everything again
the generic tools are less powerful/can't make use of Java-specific information
yeah. Its because java bytecode is executed in JVM that's why jvm has better context of the runtime information. correct me If I'm wrong.
That's one thing (or a simplified version) but there's a bit more to it
a part of it is that bytecode has a lot of useful information
but in profiling we usually look at info like memory and cpu usage right?
and then there are many things like JIT compilation and other dynamic stuff in Java
how does bytecode has this info?
it isn't just about the total usage
you want to know what exactly uses so much memory/CPU or causes other issues
seems like I need to read about other things before diving into profiling
this
The goal about profiling is to know what costs you performance/what you can improve
And there's also JVM-TI (which is an API provided by the JVM)
JVM-TI is used for things like debugging etc
and ofc there's the capability of agents in the JVM
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.