You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Chris Gunnink (JIRA)" <ji...@apache.org> on 2013/06/19 16:07:25 UTC

[jira] [Created] (WICKET-5241) RequestLogger's server duration does not include 'detach duration'

Chris Gunnink created WICKET-5241:
-------------------------------------

             Summary: RequestLogger's server duration does not include 'detach duration'
                 Key: WICKET-5241
                 URL: https://issues.apache.org/jira/browse/WICKET-5241
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 6.6.0
            Reporter: Chris Gunnink
            Priority: Minor


When a certain IModel impl takes a lot of time to detach, this will not be included in the 'duration' section. This is very easy to reproduce: use a model that sleeps for 10 seconds in the detach(); make sure to write a page which will not much time to render, say 100ms. One will see that the RequestLogger will output 100ms as duration, instead of 10100ms.

In our production environment, these this server duration is the primary metric to show server performance; so right now we're dealing with misleading figures.

I hope this is an easy one to fix ;-)

--
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