[
http://jira.jboss.com/jira/browse/JBSEAM-3024?page=all ]
Alex Savitsky updated JBSEAM-3024:
----------------------------------
Attachment: Perf.zip
Eclipse WST project in Maven format. Either import it into Eclipse (requires Maven 2
eclipse plugin), or build WAR using Maven.
After deploying, access the home page, and observe the page load times for first and
subsequent accesses. My average was about 1.3-1.5 seconds (FasterFox page load timers are
useful here).
Now, update Seam version in POM from 2.0.2.GA to 2.0.1.GA, and repeat the above steps. The
observed average load times will be much lower (0.3-0.4 seconds in my case).
Keep in mind, this is a very simplified version of the actual application I had first
observed this issue with. I've tried to preserve the general architecture used, but
scaled back on # of controls and DB entities. The actual app executes queries on a
four-level deep entity hierarchy, and also uses Tomahawk sortable headers, resulting in
load times of about 30 seconds for 2.0.2 (as opposed to about 3 seconds on 2.0.1)
Performance issues in 2.0.2 release
-----------------------------------
Key: JBSEAM-3024
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3024
Project: Seam
Issue Type: Bug
Affects Versions: 2.0.2.GA
Reporter: Alex Savitsky
Attachments: Perf.zip
For pages accessing components with many injections/outjections, performance is roughly
4x times worse when upgrading from 2.0.1 GA to 2.0.2 GA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira