[ 
https://issues.apache.org/jira/browse/OPENEJB-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Howard W. Smith, Jr. updated OPENEJB-1955:
------------------------------------------

    Attachment: jvisualvm.nps
                jvisualvm.html
                jvisualvm.csv

Deployed latest app changes to production server (Windows 2003 Server 32bit 4GB 
RAM).

jvisualvm output files attached only includes app startup, user login, and 
first page that is displayed to user after successful user login.

In other words, this test is primarily testing to see how long it takes for 
pf_OrdersController to be initialized in/by the container. Please note, 
pf_OrdersController is CDI @SessionScoped bean that uses @Inject (and MyFaces 
CODI BeanManagerProvider) to inject other CDI @SessionScoped (and 
@RequestScoped) beans.

also, please note that today's latest app changes was an attempt to avoid CDI 
cyclic references; that is why I used MyFaces CODI BeanManagerProvider to the 
best of my ability to accomplish this.

The test result is still unsatisfactory; the web app is still very very (or 
'too') slow to push this TomEE/CDI web app version to 'production.

Of course, per this JIRA/issue, I am attempting to 'tune' the app, especially 
all CDI managed beans, so this TomEE/CDI web app version will perform 'better 
than' or similar to Glassfish3.1.2.2/JSF-managed-beans web app that is 
currently in production...on production server.
                
> TomEE 1.5.1 SNAPSHOT running slow on my production server; may be caused by 
> Atmosphere
> --------------------------------------------------------------------------------------
>
>                 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: 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 JSF 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).
> Per Romain and Mark, I ran jvisualvm, and it appears as though Atmosphere 
> 'may' be slowing down the web app, or the root cause.
> 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

Reply via email to