Skip to main content

JPA Performance settings Explained

Lets consider this simple Entity, Ignore @SecondaryTables and other annotations if you are not familiar with just focus on @Basic, @OneToOne, @OneToMany annotations and get ready to answer these questions.

@Entity
@SecondaryTables({
    @SecondaryTable(name="Employee_Comments")
})
public class Employee implements Serializable {

    private static final long serialVersionUID = 1L;
    @Id
    private Long id;
    @Column(name = "name")
    private String name;
    @Basic(fetch = FetchType.LAZY)
    @Column(name = "comments", table = "Employee_Comments")
    private String comments;
    @OneToMany
    private List tags = new ArrayList();

    @OneToOne(fetch=FetchType.LAZY)
    private Address address;
..
}

What happens when we load the above entity using em.find or by executing some select query ?

  1.   "comments" is Eagerly loaded
  2.   "comments" is Lazily loaded
  3.   "address" is Eagerly loaded
  4.   "address is Lazily loaded
  5.   "tags" is Eagerly loaded
  6.   "tags" is Lazily loaded
You might have guessed 2, 4 and 6 or 1, 3, 6 though neither of these are correct.

Since

@Basic(fetch = FetchType.LAZY)
@OneToOne(fetch=FetchType.LAZY)
@OneToMany(fetch=FetchType.LAZY)


 Are just "hints" to the JPA provider and its not mandatory for JPA provider to implement them, So their is no quarantee that these objects when loaded will be lazily loaded.

Conclusion : Entities heavily using above annotations and also if we load and them in bulk could seriously cause performance bottlenecks, however there are nice ways of loading entities with trim data using "Contructor" Queries. which will be topic of my next thread.

Reference JPA Specs.

http://jcp.org/aboutJava/communityprocess/final/jsr317/index.html
JPA 2.0 Specification document Page 364

"FetchType fetch (Optional) Whether the value of the field or property
should be lazily loaded or must be eagerly fetched. The
EAGER strategy is a requirement on the persistence provider
runtime that the value must be eagerly fetched. The
LAZY strategy is a hint to the persistence provider runtime.
EAGER "

@OneToOne(fetch=FetchType.LAZY)
JPA 2.0 Specification document Page 402
Also have the same comment 


@OneToMany(fetch=FetchType.LAZY)
JPA 2.0 Specification document Page 400Also have the same comment 

Comments

Post a Comment

Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     pub...
21 comments
Read more

Validating CSV Files

What is CsvValidator ?   A Java framework which validates any CSV files something similar to XML validation using XSD. Why should I use this ?   You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference. Why did I write this ?   Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing. What is the license clause ?   GNU GPL v2 Are there any JUnit test cases for me checkout ?  Yes,  source How to integrate in my existing project ? Just add the Jar which can be downloaded from here  CsvValidator.jar  and you are good. Instantiate  CsvValidator c onstructor which takes these 3 arguements          // filename is the the file to be validated and here ...
7 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column ...
11 comments
Read more