--- On Sun, 2/1/09, is_maximum mnr...@gmail.com wrote:
From: is_maximum mnr...@gmail.com
Subject: Re: [URGENT] performance issues
To: users@openjpa.apache.org
Date: Sunday, February 1, 2009, 10:33 PM
Hi Kevin,
Sorry for replying late, I was facing a rush of work.
Well we didn't change
classes used for testing.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2241065.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues
classes used for testing.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2241065.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Pinaki Poddar on 29/01/09 05:09, wrote:
2. Build-time enhancement i.e. to execute one command after compilation
performs best and minimizes complexity of load-time-weaving. I have never
understood what really makes people to avoid 'build-time enhancement' -
especially when most of the apps are
requests will fail
because their fetched entity is no longer valid. As I know using
optimistic locking is not a good option for the entities with very
frequent update actions.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2238071.html
Sent
classes used for testing.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2239148.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
/enhancer.xml
It shows one way to enhance 100's of Entity classes used for testing.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2241065.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
--performance-issues-tp2232295p2232295.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
--performance-issues-tp2232295p2232295.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2233824.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2232295.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2233824.html
Sent from
locking is
not a good option for the entities with very frequent update actions.
--
View this message in context:
http://n2.nabble.com/-URGENT--performance-issues-tp2232295p2237146.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
11 matches
Mail list logo