The Artima Developer Community
Sponsored Link

Java Buzz Forum
December 2012 New Java Performance Tips

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
News Manager

Posts: 44889
Nickname: newsman
Registered: Apr, 2003

News Manager is the force behind the news at Artima.com.
December 2012 New Java Performance Tips Posted: Dec 26, 2012 2:18 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by News Manager.
Original Post: December 2012 New Java Performance Tips
Feed Title: JavaPerformanceTuning.com
Feed URL: http://www.javaperformancetuning.com/newsletters.rss
Feed Description: JavaPerformanceTuning.com lists all the information and resources available for Java performance tuning
Latest Java Buzz Posts
Latest Java Buzz Posts by News Manager
Latest Posts From JavaPerformanceTuning.com

Advertisement
The latest Java performance tips from around the web, such as "The USE (utilization, saturation, and errors) methodology for identifying performance issues is for early use in a performance investigation to identify systemic bottlenecks quickly. It can be summarized as: For every resource, check utilization, saturation, and errors. Utilization is the percentage of time that the resource is busy servicing work during a specific time interval; Saturation is the degree to which a fully utilized resource has extra work pending; errors include retries as well as failures (retries often indicate a performance issue). Resources to monitor include: CPU utilization per core; CPU run-queue length; CPU faults; Avalable free memory; paging/swapping; failed mallocs; network IO utilization; NIC saturation; storage controller utilization; storage device utilization; storage device wait queue length; storage device error count; lock utilization (how long the locks were held); lock saturation (the number of threads waiting to acquire the lock); thread pool utilization (busy vs idle threads); thread pool saturation (waiting requests count); process/thread errors (e.g. can't fork); file descriptor errors (e.g. can't allocate/create)."

Read: December 2012 New Java Performance Tips

Topic: Using Apache Commons Functor functional interfaces with Java 8 lambdas Previous Topic   Next Topic Topic: Object and Class level locks in Java


Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2014 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use - Advertise with Us