Another example: tez.task-specific.launch.cmd-opts.list="Map 1[1,10,20]" would profile tasks 1, 10, 20 tasks in Map 1. If you need to specify for multiple vertices, just add it with ",". E.g "Map 1[1,10,20],Map 2[5,10]" and so on.
~Rajesh.B On Tue, Aug 25, 2015 at 2:04 PM, Rajesh Balamohan <[email protected]> wrote: > You can use "tez.task-specific.launch.cmd-opts.list" and > "tez.task-specific.launch.cmd-opts" to specify which tasks in which > vertices should be profiled. > > E.g > > --hiveconf tez.task-specific.launch.cmd-opts.list=“M5[0]" --hiveconf > tez.task-specific.launch.cmd-opts="-agentpath:/opt/yourkit/bin/linux-x86-64/libyjpagent.so=disablej2ee,tracing,alloceach=1000,onexit=snapshot,tracing_settings_path=/tmp/walltime.txt,dir=/tmp/__VERTEX_NAME__/__TASK_INDEX__" > > Here, Task 0 in vertex M5 would be profiled (i.e the set of profiling > options would be added to JVM start up). Once the profiling is done, it > would store the snapshot in /tmp/M5/0 directory in the node where M5-task0 > got executed. Basically __VERTEX_NAME__ would be replaced by vertexName and > __TASK_INDEX__ would be replaced by task number. > > ~Rajesh.B > > On Tue, Aug 25, 2015 at 1:57 PM, [email protected] <[email protected]> > wrote: > >> When I use mr , I can enable profile by set follow config: >> set mapreduce.task.profile=true; >> set mapreduce.task.profile.maps=0-; >> set mapreduce.task.profile.reduces=0-; >> set mapreduce.task.profile.params=-Xprof; or set >> mapreduce.task.profile.params=-agentpath:/usr/jprofile/jprofiler9/bin/linux-x64/libjprofilerti.so=port=8849,nowait; >> >> >> In tez how to enable profile? >> >> ------------------------------ >> [email protected] >> > >
