| Re: [eclipselink-users] startup time |
|
Jose, Hi, statically weaved entity classes should not affect runtime performance as they are created at design time. However, we would be interested in the details of your performance slowdown and would need these to be able to narrow down any timing issues and rule out the derby java process. Could you post one or more of the following to your bug so we can track down the timing. - log a bug at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EclipseLink - turn logging to finest and post the logs <property name="eclipselink.logging.level" value="FINEST"/> - turn on the performance profiler to get MS timing details http://wiki.eclipse.org/Optimizing_the_EclipseLink_Application_(ELUG)#Measuring_EclipseLink_Performance_with_the_EclipseLink_Profiler - optionally turn on the java se profiler to rank bottlenecks - attach the general view containing the 4 graphs in JConsole for both the Derby JVM and your app JVM processes - check out the performance page http://wiki.eclipse.org/EclipseLink/Performance http://wiki.eclipse.org/EclipseLink/Development/Performance - post as much as your SE client or a simplified unit test that reproduces the issue as you are able. thank you /michael bht@xxxxxxxxxxxxx wrote: It might help in your case if you could post a variation of your application as a bug, with your timing information. This has multiple benefits, including easy access to the problem for people who can help you. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=312146 for an example. This one does not have -javaagent:eclipselink.jar I think. Regards, Bernard |