For Tez containers, you can specify JVM args via hive.tez.java.opts config setting, there’s probably a similar setting for MR. You can add the profiler agent to this setting, there e.g. for Yourkit something like: "-agentpath:/opt/yourkit/bin/linux-x86-64/libyjpagent.so=disablej2ee,disabl etracing,dir=/tmp/ykdumps,sampling" or for JMC that is built in on some versions of JVM something like "-XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,dumponexit=true,dumponexitp ath=/tmp/jmcdumps,disk=true,repository=/tmp/jmcdumps;”. Then look at profiler dumps.
On 15/10/19, 23:45, "Justin Wong" <[email protected]> wrote: >Hi there, > >I'm recently doing a research program about hive, and I need to profile >the internal performance >of Hive. > >I've managed to run hive over hadoop localJobRunner and attached >JProfiler to it, while the CPU >hostspot stopped at level "runJar". I also tried hadoop's built in >profiling, but not profiling >log was generated. > >Could you give me some advises of profiling hive internal? > >Cheers, >-- >Justin Wong > >Blog: https://bigeagle.me/ >Fingerprint: 15CC 6A61 738B 1599 0095 E256 CB67 DA7A 865B AC3A
