[TAP5-2447] Reset conduit states with only one access to PerthreadMap

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: tapestry-core
• Labels: patch performance
• Assignee: Unassigned
• Reporter: Michael Mikhulya
• Created: 30/Jan/15 15:42
• Updated: 18/Feb/15 14:01

Description

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.