Michael Miller created DAFFODIL-2222:
----------------------------------------
Summary: InfosetInputter cached DaffodilTunables
Key: DAFFODIL-2222
URL: https://issues.apache.org/jira/browse/DAFFODIL-2222
Project: Daffodil
Issue Type: Bug
Components: Performance
Affects Versions: 2.4.0
Reporter: Michael Miller
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?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
