tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard W. Smith, Jr. (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENEJB-1955) TomEE 1.5.1 SNAPSHOT (and CDI beans) running slow on my production server
Date Thu, 29 Nov 2012 03:00:58 GMT

    [ https://issues.apache.org/jira/browse/OPENEJB-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506176#comment-13506176
] 

Howard W. Smith, Jr. commented on OPENEJB-1955:
-----------------------------------------------

Since I still have Glassfish 3.1.2.2 and JSF managed beans web application running on production
server, I like to compare speed and performance. I know EclipseLink comes bundled with Glassfish,
so I really think Glassfish is running web apps with optimized parameters to EclipseLink,
because queries are fast.

I'm wonder if TomEE is leaving it up to developer to fully optimize JPA within apps.

I know TomEE would love to gain Glassfish users. Maybe it is a good idea for TomEE to optimize
as much as possible for developers, especially for those migrating from Glassfish.
                
> 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

Mime
View raw message