• Post Reply Bookmark Topic Watch Topic
  • New Topic

OPTIMISTIC Concurrency strategy  RSS feed

 
Marco Barenkamp
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey folks,
we are currently facing a major performance problem in our j2ee app. As we all know, j2ee is no a synonym for performance, but some usecases are
that much slow. We are trying to avoid unneccessary db traffic by modifying the concurrency strategy. We are using BEA WL8.1 used DATABASE as strategy. But it came out that no other application will modify the data, so we will decice to change to OPTIMISTIc, in order to reduce the calls of ejbload().
Before we will do that effort, I would like to know if anybody has some experience in tuning database traffic.
To say it short: Will it really increase performance in a measurable manner or is it just a peanut? Thanks in advance.
 
Karthik Guru
Ranch Hand
Posts: 1209
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You will see a HUGE improvement if you enable cache-between-transactions as well. But watch out for some buggy CMR behaviour. Test out the workflows thoroughly.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!