[DAFFODIL-2222] InfosetInputter cached DaffodilTunables

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.6.0
• Component/s: Performance
• Labels: beginner
• Assignee: Unassigned
• Reporter: Michael Miller
• Created: 24/Oct/19 01:25
• Updated: 10/Feb/20 14:04
• Resolved: 28/Jan/20 19:47

Description

Is it possible to allow the InfosetInputter, and subclasses, to have a DaffodilTunables object pre-created passed into its constructor?

When profiling unparse performance, some class/resource loaders do not handle the DaffodilTunables initialization very well. In particular, if your using a container like Wildfly, the ModuleClassLoader is very inefficient, and hits disk io heavily, during the getResource("/daffodil-config.xml") that happens for every single InfoSetInputter construction.

Is it necessary to have a newly generated DaffodilTunables everytime an unparse is called?

If the above is not possible, is there a way to reuse InfosetInputter objects and reset them for repeated calls to avoid the new DaffodilTunables() overhead?