Michael Hind wrote:
Steve Blackburn wrote:
Hi Will,
As a lurker on this list, I thought I'd share the following article:
http://www.osnews.com/story.php?news_id=10729
This might be a good article for those new to JVMs. It's not as
technical as the various white paper citations being
Stefano wrote:
Mike,
how do the above strategies compare to RISC-ification of CPU bytecode
that happens in modern superscalar CPUs?
do you think there is something to learn there? or has been already?
--
Stefano, honestly curious.
Hi Stefano,
I don't see the connection,
On 6/4/05, Michael Hind [EMAIL PROTECTED] wrote:
Instead, modern JVMs try to balance these compilation burps by using a
strategy (selective optimization) that tries to ensure a method really is
important enough to invoke the JIT on. This is often done by counting the
number of times a method
Steven Gong wrote:
Is the sampling process done before running or during runtime?
The sampling is done at runtime.
(There is not much advantage in using anything other than full
optimization for anything that is compiled ahead of time. However, even
ahead of time compiled methods, such as
Steven Gong wrote:
Is the sampling process done before running or during runtime?
Sampling, like counter incrementing, is done at runtime. They are both
runtime profiling techniques to try to ascertain what methods are
important. The profile (whether method counts or samples) is used
Hi,
As a lurker on this list, I thought I'd share the following article:
http://www.osnews.com/story.php?news_id=10729
This might be a good article for those new to JVMs. It's not as technical
as the various white paper citations being bandied about but it's a nice
introduction to
