Re: [URGENT] performance issues

2009-02-02 Thread Kevin Sutter
--- 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

Re: [URGENT] performance issues

2009-02-01 Thread is_maximum
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

Re: [URGENT] performance issues

2009-01-30 Thread Kevin Sutter
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.

Re: [URGENT] performance issues

2009-01-29 Thread Adam Hardy
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

Re: [URGENT] performance issues

2009-01-29 Thread is_maximum
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

Re: [URGENT] performance issues

2009-01-29 Thread Pinaki Poddar
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.

Re: [URGENT] performance issues

2009-01-29 Thread is_maximum
/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.

[URGENT] performance issues

2009-01-28 Thread is_maximum
--performance-issues-tp2232295p2232295.html Sent from the OpenJPA Users mailing list archive at Nabble.com.

Re: [URGENT] performance issues

2009-01-28 Thread is_maximum
--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.

Re: [URGENT] performance issues

2009-01-28 Thread Kevin Sutter
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

Re: [URGENT] performance issues

2009-01-28 Thread Pinaki Poddar
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.