You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Claude Brisson (JIRA)" <ji...@apache.org> on 2016/07/19 07:46:20 UTC
[jira] [Resolved] (VELOCITY-815) MapGetExecutor is very slow
[PATCH]
[ https://issues.apache.org/jira/browse/VELOCITY-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson resolved VELOCITY-815.
-------------------------------------
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
Patch applied.
> MapGetExecutor is very slow [PATCH]
> -----------------------------------
>
> Key: VELOCITY-815
> URL: https://issues.apache.org/jira/browse/VELOCITY-815
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.7.x, 2.x
> Reporter: Oswaldo Hernandez
> Assignee: Claude Brisson
> Labels: perfomance
> Fix For: 2.x
>
> Attachments: VELOCITY-815.patch
>
>
> When MapGetExecutor is instantiated by the UberspectImpl it iterates through all the interfaces implemented by the object's Class to figure out whether it's a java.util.Map
> This could be replaced by an instance of test on the object received by the Uberspect which would be much faster. We noticed this as a hotspot after upgrading to 1.6 through our Performance Tests JProfiler output.
> I am happy to provide a patch for this, it would be nice to get this on the maintenance branch as well if possible, so that we don't have to maintain a fork until we upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org