4/4/2023 0 Comments Jprofiler tutorial pdf![]() ![]() Confluence: How to analyze thread dumpsĪnalysing thread dumps is all about removing the noise and finding something meaningful.This varies between operating systems, but Atlassian has made guides that cover all the things that need to be taken into account. This seems to be a good middle ground that catches threads that long running, but doesn't include too much noise from the standard operation of an instance. My recommendation, as a starting point, is always a total of 6 thread dumps, one taken every 10 seconds. Too close together, and we may be swamped with too much information. Also, if we take the thread dumps too far apart, we may miss information. Note that thread dumps are only useful is gathered while the problem is happening. ![]() ![]() However, it's important they're gathered in a meaningful way. If an instance is seeing performance problems, thread dumps should always be gathered. Thread dumps are second to only application logs in how many problems they will help solve. If we were analysing the thread dumps, this one would be pretty safe to ignore. ![]() This means the thread is connected to a client, and is either in the process of getting data sent to it, or waiting to time out after data has already been sent to it. In our example, this thread is reading from a socket. This is a breakdown of exactly what that particular thread was doing at the instant this thread dump was taken. We'll talk more about what these states mean later, but for more information about this, check out the Java docs on thread state. Threads can be in a few different states:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |