You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Michael Mikhulya (JIRA)" <ji...@apache.org> on 2014/05/19 18:31:39 UTC
[jira] [Updated] (TAP5-2334) Decrease number of operations with
HashMap #1
[ https://issues.apache.org/jira/browse/TAP5-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Mikhulya updated TAP5-2334:
-----------------------------------
Attachment: 0001-TAP5-2334-Decrease-number-of-operations-with-HashMap.patch
> Decrease number of operations with HashMap #1
> ---------------------------------------------
>
> Key: TAP5-2334
> URL: https://issues.apache.org/jira/browse/TAP5-2334
> Project: Tapestry 5
> Issue Type: Improvement
> Reporter: Michael Mikhulya
> Labels: performance
> Attachments: 0001-TAP5-2334-Decrease-number-of-operations-with-HashMap.patch
>
>
> During profiling I found that there is a lot of work with HashMap inside tapestry framework.
> With following patch time per request decreased on 2.2ms (4.6% of overall time). Measurements were done with apache benchmark on a real application after warm up phase.
> The idea behind the patch is to get rid of double lookup inside HashMap (or event triple lookup) whenever only one lookup is enough.
> Also this patch decrease number of ThreadLocal.get calls in two times by moving PerThreadServiceCreator functionality into PerthreadManager.
--
This message was sent by Atlassian JIRA
(v6.2#6252)