struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (WW-3456) Input field tags performance degradation on POST versus GET.
Date Wed, 18 Dec 2013 06:53:09 GMT

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

Lukasz Lenart resolved WW-3456.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.3.16
         Assignee: Lukasz Lenart

With the latest release you can keep FreeMarker cache enabled event when running in devMode,
thus solves the problem with performance.

> Input field tags performance degradation on POST versus GET.
> ------------------------------------------------------------
>
>                 Key: WW-3456
>                 URL: https://issues.apache.org/jira/browse/WW-3456
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.0.11.2
>         Environment: Operating System: Solaris 10, CPU: UltraSPARC T1 (32 1Ghz proccessors),
Application server: glassfish V2
>            Reporter: Tom Rispoli
>            Assignee: Lukasz Lenart
>             Fix For: 2.3.16
>
>
> I have a JSP that uses s:iterator to display a large number of rows (up to 2000), each
row contains input fields displayed using s:checkbox and s:textfield.  When the page is initially
opened (the request is done using an http GET) the s:checkbox tag averages from .0028 to .0033
seconds to run and the s:textfield averages from .008 to .012 seconds.  Once the page is opened
on the browser and the form is submitted (an http POST) then when the JSP renders the data
(same code on the JSP generating html for the same data) the times get much slower.  The s:checkbox
averages from .018 to .008 seconds and the s:textfield averages from .027 to .049 seconds.
 
> There is a custom tag that is used on the rows as well, it uses OGNL to get its value
but its performance remains the same (around .0004 seconds) for all requests, so it doesn't
appear to be OGNL that is causing this behavior.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message