Java Application Performance

-
Java Application Performance

Java performance refers to the speed and efficiency of a Java application or system, and is typically measured by the amount of time it takes to complete a particular task or the amount of resources it uses to do so. 
Performance is a critical factor in many applications, particularly those that require real-time processing, high throughput, or low latency.

5 Common Java Performance Problems
  a) Memory Leaks and Out of Memory Errors
  b) Thread Deadlocks
  c) Garbage Collection
  d) Code-Level Issues
  e) Pool Connections

Steps to improve the performance of Java applications:
  1) Choose the Performance Parameters to Tune
      Footprint - Memory and CPU
      Throughput - Work
      Latency - Time
  2) Identify the System’s Limits
  3) Use a Profiler to Handle Bottlenecks
  4) Create a Performance Test Suite

8 Tips for Optimizing and Improving Java Performance:
  1) Avoid Writing Long Methods
  2) Use PreparedStatement instead of Statement.
  3) Use Caching
  4) Use Stored Procedures Instead of Queries.
  5) Leverage StringBuilder. 
  6) Optimize If-Else Statements. 
  7) Don't Over-optimize. 
  8) Use Java Profilers. - 

12 Tips to Optimize Java Code Performance
  1. Avoid Writing Long Methods
  2. Avoid Multiple If-else Statements
  3. Avoid Getting the Size of the Collection in the Loop
  4. Avoid Using String Objects For Concatenation
  5. Use Primitive Types Wherever Possible
  6. Avoid Using BigDecimal Class - BigDecimal uses a lot of memory
  7. Avoid Creating Big Objects Often
  8. Use Stored Procedures Instead of Queries
  9. Using PreparedStatement instead of Statement
  10. Use of Unnecessary Log Statements and Incorrect Log Levels
  11. Select Required Columns in a Query
  12. Fetch the Data Using Joins

JDK Monitoring Tools and Commands
jconsole: The jconsole command to start a graphical console to monitor and manage Java applications.
jps: The jps command to list the instrumented JVMs on the target system.
jstat: The jstat command to monitor JVM statistics.
jstatd: The jstatd command to monitor the creation and termination of instrumented Java HotSpot VMs.
jstack - jstack is a command-line JDK utility we can use to capture a thread dump. 
jvisualvm is a tool with a graphical user interface that lets us monitor, troubleshoot, and profile Java applications



Comments

Post a Comment

Popular posts from this blog

PL/SQL

-
PL/SQL PL/SQL stands for Procedural Language extensions to the Structured Query Language (SQL). PL/SQL can execute a number of queries in one block using single command. One can create a PL/SQL unit such as procedures, functions, packages, triggers, and types, which are stored in the database for reuse by applications. The PL/SQL engine resides in the Oracle engine. The Oracle engine can process not only single SQL statement but also block of many statements. Structure of PL/SQL Block: DECLARE     declaration statements; BEGIN     executable statements EXCEPTIONS     exception handling statements END; / Example : SET SERVEROUTPUT ON; SQL> DECLARE        var varchar2(40) := 'I love GeeksForGeeks' ;      BEGIN        dbms_output.put_line(var);      END;      / PL/SQL Functions PL/SQL functions are reusable blocks of code that can be used to perform specific tasks. They are...
Read more

JAVA8 Features

-
Java8 Features 1) Lambda Expressions : Concise functional code using ->. Lambda Expression basically expresses an instance of the functional interface, Lambda Expression provides a clear and concise way to represent a method of the functional interface using an expression. 2) Functional Interfaces : Single-method interfaces. An interface that contains only one abstract method is known as a functional interface. There is no restriction, that can have n number of default and static methods inside a functional interface. A functional interface is an interface that contains only one abstract method.  @FunctionalInterface annotation is used to ensure that the functional interface can’t have more than one abstract method. Runnable, ActionListener, and Comparable are some of the examples of functional interfaces.   Runnable –> This interface only contains the run() method.   Comparable –> This interface only contains the compareTo() method.   ActionListener –> ...
Read more

Build Automation

-
ANT: Ant was the first build tool released in 2000. Ant was developed on procedural programming idea. Ant was improved with an ability to accept plug-ins and dependency management over the network, with the help on Apache-IVY. Drawbacks: 1) XML is used as a format to write the build scripts. 2) Being hierarchical is not good for procedural programming, and 3) XML is relatively unmanageable.   MAVEN: Maven was introduced in 2004. Maven relied on the conventions and was able to download the dependencies over the network. Benefits : Life cycle of Maven, while following the same life cycle for multiple projects continuously. Problems: 1) Maven does not handle the conflicts between versions of the same library. 2) Complex customised build scripts are difficult to write in Maven, as compared to writing the build scripts in ANT. GRADLE : Gradle came into picture in 2012 Features  Declarative builds and build-by-convention 1) Gradle is available with separate Domain Specific Language ...
Read more