The address of the JobTracker (NameNode) is specified using *
mapred.job.tracker* (*fs.default.name*) in the configurations. When the
JobTracker (NameNode) starts, it will listen on the address specified by *
mapred.job.tracker* (*fs.default.name*); and when a TaskTracker (DataNode)
starts, it will
I think the upside about JRockit JVM is that it has very efficient tools for
profiling (e.g., Jrockit Mission Controller), which is very useful for
performance tuning. For SUN JVM, the profiling tools are either primitive or
very inefficient. Any lock with profiling Hadoop with SUN JVM?
Thanks,
-J
There are a lot of tuning "knobs" for the JRockit JVM when it comes to
performance; those tuning can make a huge difference. I'm very interested if
there are some tuning tips for Hadoop.
Grace, what are the parameters that you used in your testing?
Thanks,
JQ
On Thu, May 7, 2009 at 11:35 PM, Ste
I believe Jrockit JVM have slightly higer startup time than the SUN JVM; but
that should not make a lot of difference, especially if JVMs are reused in
0.19.
Which Hadoop version are you using? What Hadoop job are you running? And
what performance do you get?
Thanks,
JQ
-Original Message---
