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

Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/30 16:51:34 UTC

[jira] [Reopened] (TAP5-2445) Reduce usage of PerthreadMap in AbstractConditional

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

Jochen Kemnade reopened TAP5-2445:
----------------------------------
      Assignee: Jochen Kemnade

Git does not respond so I'll reopen this until I'm able to push the changes.

> Reduce usage of PerthreadMap in AbstractConditional
> ---------------------------------------------------
>
>                 Key: TAP5-2445
>                 URL: https://issues.apache.org/jira/browse/TAP5-2445
>             Project: Tapestry 5
>          Issue Type: Sub-task
>          Components: tapestry-core
>            Reporter: Michael Mikhulya
>            Assignee: Jochen Kemnade
>            Priority: Minor
>              Labels: patch, performance
>             Fix For: 5.4
>
>         Attachments: 0001-Reduce-usage-of-PerthreadMap.patch
>
>
> Probably this patch is curious to those who is not familiar with tapestry internals.
> It reduces number of accesses to PerthreadMap from 2 to 1 or 0 for each beginRender call.



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