import{_ as l,o as i,c as r,a as s,b as n,w as o,e as a,d as t,r as c}from"./app.6c27e557.js";const u={},d=s("h1",{id:"trace",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#trace","aria-hidden":"true"},"#"),a(" trace")],-1),m={href:"https://arthas.aliyun.com/doc/arthas-tutorials.html?language=en&id=command-trace",target:"_blank",rel:"noopener noreferrer"},k=s("code",null,"trace",-1),b=a(" online tutorial"),h=t('
TIP
Trace method calling path, and output the time cost for each node in the path.
trace
can track the calling path specified by class-pattern
/ method-pattern
, and calculate the time cost on the whole path.
Name | Specification |
---|---|
class-pattern | pattern for the class name |
method-pattern | pattern for the method name |
condition-express | condition expression |
[E] | enable regex match, the default behavior is wildcards match |
[n:] | execution times |
#cost | time cost |
[m <arg>] | Specify the max number of matched Classes, the default value is 50. Long format is [maxMatch <arg>] . |
There's one thing worthy noting here is condition expression
. The condition expression
supports OGNL grammar, for example, you can come up a expression like this "params[0]<0"
. All OGNL expressions are supported as long as they are legal to the grammar.
Many times what we are interested is the exact trace result when the method call takes time over one particular period. It is possible to achieve this in Arthas, for example: trace *StringUtils isBlank '#cost>100'
means trace result will only be output when the executing time exceeds 100ms.
TIP
watch
/stack
/trace
, these three commands all support #cost
.
$ trace demo.MathGame run
Press Q or Ctrl+C to abort.
Affect(class-cnt:1 , method-cnt:1) cost in 28 ms.
\`---ts=2019-12-04 00:45:08;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[0.617465ms] demo.MathGame:run()
\`---[0.078946ms] demo.MathGame:primeFactors() #24 [throws Exception]
\`---ts=2019-12-04 00:45:09;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[1.276874ms] demo.MathGame:run()
\`---[0.03752ms] demo.MathGame:primeFactors() #24 [throws Exception]
TIP
The #24
in the result indicates that in the run function, the primeFactors()
function was called on line 24
of the source file.
$ trace demo.MathGame run -m 1
Press Q or Ctrl+C to abort.
Affect(class count: 1 , method count: 1) cost in 412 ms, listenerId: 4
\`---ts=2022-12-25 21:00:00;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@b4aac2
\`---[0.762093ms] demo.MathGame:run()
\`---[30.21% 0.230241ms] demo.MathGame:primeFactors() #46 [throws Exception]
\`---ts=2022-12-25 21:00:10;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@b4aac2
\`---[0.315298ms] demo.MathGame:run()
\`---[13.95% 0.043995ms] demo.MathGame:primeFactors() #46 [throws Exception]
If the method invoked many times, use -n
options to specify trace times. For example, the command will exit when received a trace result.
$ trace demo.MathGame run -n 1
Press Q or Ctrl+C to abort.
Affect(class-cnt:1 , method-cnt:1) cost in 20 ms.
\`---ts=2019-12-04 00:45:53;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[0.549379ms] demo.MathGame:run()
+---[0.059839ms] demo.MathGame:primeFactors() #24
\`---[0.232887ms] demo.MathGame:print() #25
Command execution times exceed limit: 1, so command will exit. You can set it with -n option.
--skipJDKMethod <value>
skip jdk method trace, default value true.$ trace --skipJDKMethod false demo.MathGame run
Press Q or Ctrl+C to abort.
Affect(class-cnt:1 , method-cnt:1) cost in 60 ms.
\`---ts=2019-12-04 00:44:41;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[1.357742ms] demo.MathGame:run()
+---[0.028624ms] java.util.Random:nextInt() #23
+---[0.045534ms] demo.MathGame:primeFactors() #24 [throws Exception]
+---[0.005372ms] java.lang.StringBuilder:<init>() #28
+---[0.012257ms] java.lang.Integer:valueOf() #28
+---[0.234537ms] java.lang.String:format() #28
+---[min=0.004539ms,max=0.005778ms,total=0.010317ms,count=2] java.lang.StringBuilder:append() #28
+---[0.013777ms] java.lang.Exception:getMessage() #28
+---[0.004935ms] java.lang.StringBuilder:toString() #28
\`---[0.06941ms] java.io.PrintStream:println() #28
\`---ts=2019-12-04 00:44:42;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[3.030432ms] demo.MathGame:run()
+---[0.010473ms] java.util.Random:nextInt() #23
+---[0.023715ms] demo.MathGame:primeFactors() #24 [throws Exception]
+---[0.005198ms] java.lang.StringBuilder:<init>() #28
+---[0.006405ms] java.lang.Integer:valueOf() #28
+---[0.178583ms] java.lang.String:format() #28
+---[min=0.011636ms,max=0.838077ms,total=0.849713ms,count=2] java.lang.StringBuilder:append() #28
+---[0.008747ms] java.lang.Exception:getMessage() #28
+---[0.019768ms] java.lang.StringBuilder:toString() #28
\`---[0.076457ms] java.io.PrintStream:println() #28
$ trace demo.MathGame run '#cost > 10'
Press Ctrl+C to abort.
Affect(class-cnt:1 , method-cnt:1) cost in 41 ms.
\`---ts=2018-12-04 01:12:02;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[12.033735ms] demo.MathGame:run()
+---[0.006783ms] java.util.Random:nextInt()
+---[11.852594ms] demo.MathGame:primeFactors()
\`---[0.05447ms] demo.MathGame:print()
TIP
Only the call path which's time cost is higher than 10ms
will be shown. This feature is handy to focus on what's needed to focus when troubleshoot.
trace
itself takes, therefore it is not as accurate as these softwares offer. More classes and methods on the calling path, more inaccurate trace
output is, but it is still helpful for diagnostics where the bottleneck is.12.033735
ms.0.005428
ms, the maximum time cost is 0.094064
ms, and the total time cost for all method calls (3
times in total) to "demo:call()" is 0.105228ms
. If "throws Exception" appears in this line, it means some exceptions have been thrown from this method calls.The trace command will only trace the subcalls in the method to the trace, and will not trace down multiple layers. Because traces are expensive, multi-layer traces can lead to a lot of classes and methods that ultimately have to be traced.
You can use the regular expression to match multiple classes and methods on the path to achieve a multi-layer trace effect to some extent.
Trace -E com.test.ClassA|org.test.ClassB method1|method2|method3
TIP
The watch/trace/monitor/stack/tt commands all support the --exclude-class-pattern
parameter
Use the --exclude-class-pattern
parameter to exclude the specified class, for example:
watch javax.servlet.Filter * --exclude-class-pattern com.demo.TestFilter
TIP
Supported since version 3.3.0.
Open terminal 1, trace the run
method in the above demo, and you can see the printout listenerId: 1
.
[arthas@59161]$ trace demo.MathGame run
Press Q or Ctrl+C to abort.
Affect(class count: 1 , method count: 1) cost in 112 ms, listenerId: 1
\`---ts=2020-07-09 16:48:11;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[1.389634ms] demo.MathGame:run()
\`---[0.123934ms] demo.MathGame:primeFactors() #24 [throws Exception]
\`---ts=2020-07-09 16:48:12;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[3.716391ms] demo.MathGame:run()
+---[3.182813ms] demo.MathGame:primeFactors() #24
\`---[0.167786ms] demo.MathGame:print() #25
Now to drill down into the sub method primeFactors
, you can open a new terminal 2 and use the telnet localhost 3658
connects to the arthas, then trace primeFactors
with the specify listenerId
.
[arthas@59161]$ trace demo.MathGame primeFactors --listenerId 1
Press Q or Ctrl+C to abort.
Affect(class count: 1 , method count: 1) cost in 34 ms, listenerId: 1
At Terminal 2 prints the results, indicating that a method has been enhanced: Affect(class count: 1 , method count: 1)
, but no more results are printed.
At terminal 1, you can see that the trace result has increased by one layer:
\`---ts=2020-07-09 16:49:29;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[0.492551ms] demo.MathGame:run()
\`---[0.113929ms] demo.MathGame:primeFactors() #24 [throws Exception]
\`---[0.061462ms] demo.MathGame:primeFactors()
\`---[0.001018ms] throw:java.lang.IllegalArgumentException() #46
\`---ts=2020-07-09 16:49:30;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@3d4eac69
\`---[0.409446ms] demo.MathGame:run()
+---[0.232606ms] demo.MathGame:primeFactors() #24
| \`---[0.1294ms] demo.MathGame:primeFactors()
\`---[0.084025ms] demo.MathGame:print() #25
Dynamic trace by specifying listenerId
, you can go deeper and deeper. In addition, commands such as watch
/tt
/monitor
also support similar functionality.
For example, in the following result: 0.705196 > (0.152743 + 0.145825)
$ trace demo.MathGame run -n 1
Press Q or Ctrl+C to abort.
Affect(class count: 1 , method count: 1) cost in 66 ms, listenerId: 1
\`---ts=2021-02-08 11:27:36;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@232204a1
\`--[0.705196ms] demo.MathGame:run()
+---[0.152743ms] demo.MathGame:primeFactors() #24
\`--[0.145825ms] demo.MathGame:print() #25
So where is the rest of the time consumed?
Methods that are not traced to. For example, methods under java.*
are ignored by default. This can be printed out by adding the -skipJDKMethod false
parameter.
$ trace demo.MathGame run --skipJDKMethod false
Press Q or Ctrl+C to abort.
Affect(class count: 1 , method count: 1) cost in 35 ms, listenerId: 2
\`---ts=2021-02-08 11:27:48;thread_name=main;id=1;is_daemon=false;priority=5;TCCL=sun.misc.Launcher$AppClassLoader@232204a1
\`--[0.810591ms] demo.MathGame:run()
+--[0.034568ms] java.util.Random:nextInt() #23
+---[0.119367ms] demo.MathGame:timeFactors() #24 [throws Exception]
+---[0.017407ms] java.lang.StringBuilder:<init>() #28
+--[0.127922ms] java.lang.String:format() #57
+---[min=0.01419ms,max=0.020221ms,total=0.034411ms,count=2] java.lang.StringBuilder:append() #57
+--[0.021911ms] java.lang.Exception:getMessage() #57
+---[0.015643ms] java.lang.StringBuilder:toString() #57
\`--[0.086622ms] java.io.PrintStream:println() #57
Instruction consumption. For example, instructions such as i++
, getfield
, etc.
Possible JVM pause during code execution, such as GC, entering synchronization blocks, etc.
TIP
The watch/trace/monitor/stack/tt commands all support the -v
parameter.
When the command is executed, there is no output result. There are two possibilities:
But the user cannot tell which situation is.
Using the -v
option, the specific value and execution result of Condition express
will be printed for easy confirmation.