• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

High Performance Java Persistence

 
Ranch Hand
Posts: 462
Scala jQuery Java
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Vlad,
There's a commonly held view that JPA implementations are slow, presumably because the standard configuration needs tweaking, are there some common issues that you see time and again that make a big difference to performance?
 
Author
Posts: 33
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, I dedicated a whole book on this topic but the most common issues are:

Strictly related to JPA:

- fetching too much data
- not using batch insert/update/deletes
- using exotic mappings that cause ineffective queries
- improper caching settings that cause many invalidations and cache misses

Related to any data access layer:

- holding too much on connections
- not properly indexing the DB queries
- not using Statement caching
reply
    Bookmark Topic Watch Topic
  • New Topic