Skip to main content

JAVA MEMORY LEAK, UTILISATION AND MONITORING USING JFR using Mission Control

JAVA MEMORY LEAK, UTILISATION AND MONITORING USING JFR using Mission Control

Java flight recording(JFR) help us to analyse and find the root cause of any slowness in our program along with CPU usage , hot methods and garbage collection , profiling etc.

To visualise we need to feed .jfr file to JDK mission control present in JDK bin folder.

After successful compilation , we should run the program with below option which will generate the .jfr and feed to mission control.

  command :  java -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:StartFlightRecording=duration=200s,filename=flight.jfr -cp ./out/ path-and-class-name


Below are some example to understand how this JFR can be helpful.

1. Lets consider we have created a java program in which we have used LinkList to store the elements and in same program we are using contains method inside a for loop of 1 million , in this case each time this contains method will be called then 1 million records will be scanned each time which can slow our program.

   To overcome this problem we should have consider HashSet instead if linkedList as data are stored in sequential way in LinkedList and using contains method increase the comparing time while in Set its O(1).

This kind of problem will be difficult to analyse from developer eyes as while developing more focus given to business logic compare to data type selection. Here JFR comes to rescue and point at exact method line as hot methods which should be looked into

2. Suppose we have synchronised a method  or block used by multiple threads but as we know synchronised block can be accessible by only one thread at a time. JFR can visualise and give you proper graphical representation  of  waiting , blocking and running time of thread and can point out exact blocking method which is causing issue.

3. Lets consider we created a Hashmap as   HashMap<Integer, String> map=new HashMap(). now we are putting key as primitive int and value as a string and we have 1 million records to put. Do you realise any issue here .

  No let me tell you, every-time you are calling put method using int as key, internally java is doing autoboxing to change the type of primitive type to Integer type. This can be visualise and can be found when you will run your program with Java mission control and will be able to see the differences after changing the type of key.



Labels:

Comments

Post a Comment

Popular posts from this blog

Java Program : Writing First Java Factorial Program with explanation

 NAMING CONVENTION IN JAVA : Java is an object oriented programming language , we can relate it to real life object like i mapped Java with human in my previous post JAVA OVERVIEW (SESSION 1)  and represent human properties like body parts as properties in Java and Human can dance , drive , walk , run these can be mapped as Behaviour in java.    Now To represent properties and behaviour in java , there are some standard naming conventions we should follow. Class name should always starts with Uppercase letter like class Student { //Code to be executed } Properties or any kind of variables should starts from lower case and afterwards every first letter of each next word should be in Upper case . like class Student { int studentId ; String studentName ; //Code to be executed } Methods name should also starts from lower case and afterwards every first letter of each next word should be in Upper case . like class Student { int studentId ; String studentName ;
2 comments
Read more

OOPS Concept in Java : ENCAPSULATION

OOPS Concept in Java : ENCAPSULATION   This OOPS concept can be used to make things simpler in case of software development . Main purpose of this concept is to hide the properties of any class and give access to fetch and modified based on business criteria.  A simple example can be a POJO ( Plain Old Java Object) in which all the properties of a class can be private and through getter and setter method of properties we can fetch and update the properties of Object. So instead of having direct access to properties we have created 2 methods to make the CLASS things encapsulated in single unit while access to it is via 2 public methods.   Just consider we have requirement that once the object is created its value should not be changed then simplest way to achieve this  can be done by just removing setter method and we will keep only getter methods to access Object properties . In this case after Object creation whatever the value of Object properties has been initialised it will b
Post a Comment
Read more

OOPS Concept in Java : POLYMORPHISM

 POLYMORPHISM IN JAVA :  Polymorphism means mutiple forms of Single reference. And to understand in simple way just take an example from my previous post of OOPS CONCEPT IN JAVA : INHERITANCE  , I request you guys to go through this link before proceding here. So in this post I have created a method called sum() in PARENT class which has been used by CHILD class without writing same sum() method in CHILD class. This was possible becuase of INHERITANCE concept in java.  But what if CHILD class is not satisfied with PARENT sum() and CHILD class wants to improve it like by adding some message before the calculation. To do this we have another OOPS CONCEPT IN JAVA i.e POLYMORPHISM and by applying this logic we can make same sum() method behvae differently based on Object. As I mentioned earlier POLYMORPHISM means different forms and same has been achieved here by calling same sum() method but the output is different based on Object on which it has been called. If Object is of PARENT
Post a Comment
Read more