On Jul 16, 12:58 am, Christian Vest Hansen <[email protected]>
wrote:
> I haven't tried to look beyond the JIT to see what it does, so I
> wouldn't know which tools to use, but if you do not already know about
> it, you might find the HotSpot Internals wiki to be an interesting
> source of info:http://wikis.sun.com/display/HotSpotInternals/Home
>
>
>
> On Thu, Jul 16, 2009 at 5:39 AM, Bradbev<[email protected]> wrote:
>
> > I see lots of discussion on this list about Clojure performance & how
> > to get it to Java speed.  I am also interested in the next steps that
> > happen, how does the JVM convert byte code down to machine code and
> > how does one examine that?
> > The profiling tools I use for C code let me look at what the compiler
> > has done with my C/C++ code & where the machine is running slow (cache
> > misses, pipeline stalls, etc).
> > JVM apps obviously have another layer of indirection, the first layer
> > is the quality of the byte code that has been generated, and then how
> > hotspot compiles that into machine code.
> > What tools are out there that let you examine the bytecode & JVM
> > machine code output?  It would also be really nice if there were tools
> > that told you why the JVM did or did not manage to optimize a block of
> > code.
>
> > I'm just curious here really, but it does seem like there are many
> > knowledgeable people on this list that might be able to offer some
> > tips.
>
> > Thanks,
> > Brad
>
> --
> Venlig hilsen / Kind regards,
> Christian Vest Hansen.
Thanks to all the replies.  Christian, the HotSpotInternals link is
great, thanks!

Brad
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to