[jira] [Updated] (TAP5-2447) Reset conduit states with only one access to PerthreadMap

["Michael Mikhulya (JIRA)" <ji...@apache.org>]

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

Michael Mikhulya updated TAP5-2447:
-----------------------------------
    Attachment: 0001-Reset-conduit-states-with-only-one-access-to-Perthre.patch

> Reset conduit states with only one access to PerthreadMap
> ---------------------------------------------------------
>
>                 Key: TAP5-2447
>                 URL: https://issues.apache.org/jira/browse/TAP5-2447
>             Project: Tapestry 5
>          Issue Type: Sub-task
>          Components: tapestry-core
>            Reporter: Michael Mikhulya
>              Labels: patch, performance
>         Attachments: 0001-Reset-conduit-states-with-only-one-access-to-Perthre.patch
>
>
> In this patch conduit states are reimplemented in the way similar to renderVariables. As result of it postRenderCleanup doesn't clean each conduit state separately.
> This patch provides about 2ms saving per page rendering on real application. So it is really valuable to at least review it.
> Seems like it not only because of reducing access to PerthreadMap, but also because decreasing number of read locks because of NamedSet usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)