Java Performance Tuning

Java(TM) - see bottom of page

|home |services |training |newsletter |tuning tips |tool reports |articles |resources |about us |site map |contact us |
Tools: | GC log analysers| Multi-tenancy tools| Books| SizeOf| Thread analysers| Heap dump analysers|

Our valued sponsors who help make this site possible
JProfiler: Get rid of your performance problems and memory leaks! 

Training online: Concurrency, Threading, GC, Advanced Java and more ... 

News April 2023

JProfiler
Get rid of your performance problems and memory leaks!

Modern Garbage Collection Tuning
Shows tuning flow chart for GC tuning


Java Performance Training Courses
COURSES AVAILABLE NOW. We can provide training courses to handle all your Java performance needs

Java Performance Tuning, 2nd ed
The classic and most comprehensive book on tuning Java

Java Performance Tuning Newsletter
Your source of Java performance news. Subscribe now!
Enter email:


Training online
Threading Essentials course


JProfiler
Get rid of your performance problems and memory leaks!


Back to newsletter 269 contents

A draft JEP has been published which, if implemented, will stop a large swathe of troubleshooting and monitoring tools from working on JVMs (without having to first restart them with an option change). The draft JEP asserts with no evidence that "most serviceability tools do not rely on dynamically loaded agents" which seems to ignore the many many projects in github that use remote agent loading.

The odd thing about this draft JEP is that it seems to be ideological only. There appears to be almost no benefit to it, but substantial downside. There would be no beneficial changes to the core JVM code from adopting it, no additional features enabled or planned to be enabled. (There would be a tiny amount of additional security, but remote agent loading is already limited by OS privileges so you must already have full access to the running JVM process and memory before you can attach).

For the tiny minority of systems that want to enforce no remote agent loading, you can already do so in any JVM9+ with the -XX:-EnableDynamicLoading option. You can even disable the attach mechanism entirely with -XX:+DisableAttachMechanism.

Every change to the JVM has benefits and disadvantages - the concrete benefits need to outweigh the disadvantages for the change to proceed, and I can't even see concrete benefits here. I can only hope ideology doesn't triumph over pragmatism and usefulness. JVM serviceability is one of the huge advantages it has over other runtimes, and reducing that capability for no benefit makes no sense to me. Now on to all the usual newsletter list of links, tips, tools, news and articles, and as usual I've extracted all the tips into this month's tips page

A note from this newsletter's sponsor

JProfiler
Get rid of your performance problems and memory leaks!

News

Java performance tuning related news

Tools

Java performance tuning related tools

Articles

Jack Shirazi


Back to newsletter 269 contents


Last Updated: 2024-10-29
Copyright © 2000-2024 Fasterj.com. All Rights Reserved.
All trademarks and registered trademarks appearing on JavaPerformanceTuning.com are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries. JavaPerformanceTuning.com is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
URL: http://www.JavaPerformanceTuning.com/news/news269.shtml
RSS Feed: http://www.JavaPerformanceTuning.com/newsletters.rss
Trouble with this page? Please contact us