RFR(XS): 8137173: @HotSpotIntrinsicCandidate is not Oracle-specific
kirk.pepperdine at gmail.com
Fri Oct 16 12:14:03 UTC 2015
I’ve updated the abstract. I hope you find this one better suited to the event.
Java Performance Tuning Workshop
> In this workshop you will be introduced to jPDM (Java Performance Diagnostic Model), a methodology that brings structure to the often adhoc activity of performance tuning. Following jPDM will help you quickly and definitivily identify root causes of performance bottlenecks. In addition, we will deep dive into different aspects of the Java stack and look at some of the tools you can use to reveal the inner workings. The talk will be augmented with a number of exercises so do bring a laptop. If you don’t have one to bring don’t fret, we encourage people to problem solve in groups. If you have one, we would encourage you share.
> Topics covered:
> 1. Performance Benchmarking
> • benchmarking basics
> • types and purpose of benchmarks
> ◦ load, stress, spike, endurance
> • finding and resolving blocking conditions
> 2. Improving observability
> • taking measures
> • logging
> • Java Management eXtensions
> 3. jPDM, a performance diagnostic model
> • using key metrics to categorize a performance bottleneck
> • OS, JVM, Application, liveliness
> 4. Garbage Collection
> • Java memory management (in a nutshell)
> • GC logging
> • GC tuning tactics
> 5. Profiling
> • Execution profiling
> • Memory profiling
> • Memory leaks
> On Oct 15, 2015, at 11:12 PM, mark.reinhold at oracle.com wrote:
> 2015/10/1 10:57 -0700, zoltan.majo at oracle.com:
>> On 10/01/2015 05:54 PM, mark.reinhold at oracle.com wrote:
>>> I suggest putting this into jdk.internal.vm.annotation, which is
>>> also a good place for the ReservedStackAccess annotation envisioned
>>> in JEP 270 (http://openjdk.java.net/jeps/270).
>> I filed an RFE, JDK-8138732: "move @HotSpotIntrinsicCandidate to the
>> jdk.internal.vm.annotation package" , to track the issue of moving
>> the annotation to a different package. I hope I can take care of it soon.
>> Thank you and best regards,
> Thanks. While you're at it, could you please rename the annotation to
> @IntrinsicCandidate? There's no need for the "HotSpot" prefix any more
> since this annotation will now be in a package that is reserved for
> VM-specific annotations.
> (Sorry for this late suggestion; this just came up in a discussion of
> the @ReservedStackAccess annotation for JEP 270, which is also destined
> for the jdk.internal.vm.annotation package.)
> (I've pasted this addendum into JDK-8138732.)
> - Mark
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-compiler-dev