[
https://issues.apache.org/jira/browse/OPENEJB-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506476#comment-13506476
]
Howard W. Smith, Jr. commented on OPENEJB-1955:
-----------------------------------------------
Jean-Louis,
Please don't quote me on Glassfish caching right out the box. All I know, my
JSF-managed-beans web app is running much faster on Glassfish 3.1.2.2 on
Windows Server 2003 32bit 4GB RAM, faster than TomEE / CDI web app on Windows
Server 2003 32bit 4GB RAM and Windows Server 2008 64bit 16GB RAM. For this
reason, I cannot push my TomEE / CDI web app to production server 'yet' and
expect endusers to appreciate the extreme slowness of responses from web app. :(
Even though I put a lot of effort in optimizing the app so far, I am not seeing
any performance improvement on Windows Server 2003 32bit platform. I think I
see performance improvement on Windows Server 2008 64bit, but I am at a loss on
optimizing web app to deploy it to TomEE on Windows Server 2003.
I am not done yet with all of my planned optimizing yet.
I'm already running JDK 1.7.07 on Windows Server 2003 32bit, but I see that
there is another JDK or JRE update available, I think it's JDK 1.7.09, right?
Maybe that addresses some issues related to Windows 32bit environments. Romain
did tell me that app will only run as good as the JVM will allow it to run.
Romain, honestly, I don't know if I'm waving the entities. I read something
about weaving, but I don't know if that's what you're talking about. Okay about
TIKA stuff; it's not a real big concern. It serializes itself on app startup
only, and living on an CDI @ApplicationScoped bean.
> 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
