[VELOCITY-815] MapGetExecutor is very slow [PATCH]

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.x, 2.0
• Fix Version/s: 2.0
• Component/s: Engine
• Labels: perfomance
• Assignee: Claude Brisson
• Reporter: Oswaldo Hernandez
• Created: 13/Jan/12 03:10
• Updated: 07/Jan/18 15:46
• Resolved: 19/Jul/16 07:45

Description

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.