[
https://issues.apache.org/jira/browse/OPENEJB-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506291#comment-13506291
]
Jean-Louis MONTEIRO commented on OPENEJB-1955:
----------------------------------------------
Hi Howard,
I read carefully all your messages and went into some VisualVM snapshots.
Maybe I missed something but did not saw significant overhead in OpenEJB/TomEE.
In some of them, I saw BVal.
Anyway, yes the query cache can provide huge improvements cause you don't have
the sql cpu time in the database itself, but you also don't have the time spent
in network, extracting results, creating objects, etc.
But, it has to be configured carefully and I'm my opinion should be primary on
read only data (reference data to name but a few).
On read/write data, the result is not that significant as you have o deal with
transaction and synchronize accesses. Moreover, in a clustered environment, you
have to set up a distributed cache which is really painful to configure and
which provide a significant overhead. In other words, it's sometimes worse that
without cache.
With that big picture in mind, I'm not sure we have to provide default settings
for cache in EclipseLink or Hibernate/OpenJPA btw.
But, that could be interesting to put a page up on the site describing possible
optimizations per JPA Provider. WDYT?
I'm happy to create the page and let you fill it with EclipseLink specific
configurations.
Are you sure that's the only difference between glassfish and TomEE?
That seems strange to me Glassfish is caching queries out of the box.
Anyway, a big thanks for your investigations and time.
> TomEE 1.5.1 SNAPSHOT (and CDI beans) running slow on my production server
> -------------------------------------------------------------------------
>
> Key: OPENEJB-1955
> URL: https://issues.apache.org/jira/browse/OPENEJB-1955
> Project: OpenEJB
> Issue Type: Question
> Components: container system
> Affects Versions: 1.6.0
> Environment: Windows Server 2003, 32-bit, PrimeFaces 3.5 SNAPSHOT,
> PrimeFaces Push (Atmosphere/websockets) configured;
> Internet connection is powered by Verizon Wireless 4G
> Reporter: Howard W. Smith, Jr.
> Priority: Minor
> Labels: 2003, atmosphere, server, tomee, windows
> Fix For: 1.6.0
>
> Attachments: 20121128_profileLogin1_getOrderNumberList.jpg,
> 20121128_profileLogin1.jpg, 20121128_profileLogin2_getOrderNumberList.jpg,
> 20121128_profileLogin2.jpg, 20121128_profileLogin3_getOrderNumberList.jpg,
> 20121128_profileLogin3.jpg, 20121128_profileLogin_filterByDynamicSQL.jpg,
> 20121128_profileLogin_filterByNamedQuery.jpg,
> 20121128_profileLogin_initOrdersController1.jpg,
> 20121128_profileLogin_initOrdersController2.jpg,
> 20121128_profileLogin_initOrdersController3.jpg, catalina.2012-11-27.log,
> jvisualvm_20121127.csv, jvisualvm_20121127.html, jvisualvm_20121127.nps,
> jvisualvm.csv, jvisualvm.html, jvisualvm.nps,
> jvisualvm_tomee_excel_smaller.csv, jvisualvm_tomee.html, jvisualvm_tomee.nps,
> jvisualvm_tomee_smaller.csv, jvisualvm_tomee_smaller.html, web.xml
>
> Original Estimate: 612h
> Remaining Estimate: 612h
>
> I was working with Romain and Mark Struberg on this one, and decided to open
> an issue, so I could attach files and continue discussion here.
> My TomEE/CDI-managed-beans web application is running really slow on
> production server (Windows Server 2003 32-bit Verizon Wireless 4G internet
> connection); runs faster on Windows Server 2008 64bit (cablemodem internet
> connection).
> Currently in production, the Glassfish 3.1.2.2 and JSF-managed-beans version
> of the web application is running much faster than the
> TomEE/CDI-managed-beans version of the web application.
> Per Romain and Mark, I ran jvisualvm to provide some benchmarks.
> Please review attached files and confirm and advise.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
