Home > Articles > Programming > Java

Charlie Hunt on Java Performance Monitoring and Tuning

  • Print
  • + Share This
Steven Haines, host of the InformIT Java Reference Guide, and Charlie Hunt, co-author of Java Performance, discuss performance issues, application monitoring, scalability vs performance, and the impact cloud computing has on application monitoring and performance management.
Like this article? We recommend

Like this article? We recommend

Steven Haines: What are the most common Java performance issues that you've seen?

Charlie Hunt: The issues generally fall into a couple different categories:

  1. At the application source code level, poor choice of algorithms or data structures. Better algorithms & data structures almost always offer the biggest performance return on investment.
  2. Unnecessary object allocation, but more importantly, unnecessary object retention. In short, high object retention is challenging for any JVM's GC to handle well and offer an application good performance.
  3. Use of un-buffered I/O.
  4. A poorly tuned JVM.
  5. High lock contention, which leads to scalability bottlenecks.
  6. Data structures re-sizing. Those data structures using arrays as a backing store.

Essentially, there's content in some form or another in the Java Performance that talks to all of the above issues and offers approaches to addressing them.

SH: Can you describe the various techniques for monitoring application performance? Is monitoring different from profiling?

CH: First, yes monitoring is quite different from profiling. In Java Performance I offer a rather detailed description of each. In short, monitoring tends to be non-intrusive on application performance, tends to be more broad than profiling, is often times done in a production environment, and is generally used to identify potential problem and present symptoms of a potential performance issue. Profiling, in contrast, can be more intrusive on application performance, tends not to be done in production, also tends to be more focused than monitoring, and prior to profiling you usually have some idea of what you are looking for in a profiling task based on what you've observed via monitoring.

In the context of a Java application, it's a common practice to monitor statistics at the operating system level, JVM level, and even at the application level. So, you need tools to collect those statistics at each level. In addition, when stakeholders complain of application performance, it's also common to monitor an application in both an online mode and offline mode. It's also common, and recommended, to collect performance statistics and evaluate them in an offline mode, even when stakeholders are not complaining of performance issues. Evaluating those performance statistics, in either an online mode or offline mode, offers clues or symptoms as to the performance issue.

SH: What has Oracle done in the Hotspot JVM to increase its performance?

CH: One way to think about this is to compare and contrast the content of Wilson and Kesselman's Java Platform Performance (Prentice Hall, 2000) book's content versus the content found in the just published Java Performance book. I think you'll find that that there's quite a bit that has changed (and improved) between their publications. I also think it's interesting to think about what were the most common Java performance issues "then versus now."

SH: Sometimes people use the terms "performance" and "scalability" interchangeably. What is the difference? And how do I measure performance and how do I measure scalability?

CH: I interpret performance to be a more abstract term than scalability. For instance, performance can mean any one of the following (could take on additional meanings in different contexts):

  1. performance throughput
  2. performance latency or responsiveness
  3. memory footprint
  4. start-up time
  5. scalability
  6. In the context of a Java application, performance could also capture the notion of the amount of elapsed time until the application reaches peak performance.

Each of the above are measured in different ways.

The recent popularity of multi-core processors and systems with multiple CPU sockets has brought scalability to the forefront as one of the most common performance issues.

Scalability is all about an application's ability to take on (or service) additional load while maintaining the same throughput and/or latency.

SH: Are there any common performance-tuning options (low hanging fruit) that most applications can benefit from?

CH: I wouldn't necessarily say there are common performance-tuning options, but rather there are some common principles that usually offer a Java application to realize better performance. Several of these from a JVM tuning perspective are presented in the Tuning the JVM, Step-by-Step chapter of the book.

In the way of JVM command line options, my recommendation to folks has always been to justify why you want to use a given JVM command line tuning option. If you can, justify its use, other than merely saying you saw the command line option being used on some other application and it appeared to help that application. This justification doesn't fly with me. Every application is different. What works well for command line options does not necessarily mean it will work well for a different application.

I would also say that choosing a given tuning option usually has its advantages and consequences. For example, when you look at throughput, latency, and footprint, you generally sacrifice something in one of those in favor of one or both of the others. As to which ones are most important depends on the application and what the application stakeholders believe is most important.

SH: How is performance management different now, with large-scale cloud-based applications running on thousands of machines, than it was a few years ago with standard n-tier applications? How is such an environment monitored?

CH: Actually, I find "cloud" to be such an overloaded term. But, I think I understand what you're asking.

As software and application deployments become more complex, so do the tools to monitor those application deployments. However, the same needs exist to monitor operating system statistics, JVM statistics and application level statistics. The one area that's impacted the most is the application level statistics monitoring. But, in general the application level statistics still tend to measure the same types of things such as end-to-end response times. It's just that a given operation may span multiple machines, or multiple "somethings" in a cloud environment (it's a bit more abstract now). But, in the end, the application statistics still tend to measure the same or similar things — end-to-end response time for example. However, you might see additional instrumentation to identify critical transition points or phases of a given operation.

In addition, it's also desirable to correlate operating system statistics, JVM statistics, and application level statistics to see if one impacts the other(s). So, as applications are moved to a cloud-based environment, the need/want remains to correlate these statistics. It just often times it becomes a little harder to do so.

In other words, the statistics of interest still remain, but being able to collect the statistics and correlate the information usually becomes a little more complex/difficult.

Charlie Hunt is the JVM performance lead engineer at Oracle. He is responsible for improving the performance of the HotSpot JVM and Java SE class libraries. He has also been involved in improving the performance of the Oracle GlassFish and Oracle WebLogic Server. A regular JavaOne speaker on Java performance, he also co-authored Java Performance and NetBeans™ IDE Field Guide.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020