[jira] [Resolved] (DAFFODIL-2222) InfosetInputter cached DaffodilTunables

["Steve Lawrence (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-2222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence resolved DAFFODIL-2222.
--------------------------------------
    Fix Version/s: 2.6.0
       Resolution: Fixed

Fixed in commit 143731d692363e0a315c560abc3d62060ae3bb86

> InfosetInputter cached DaffodilTunables
> ---------------------------------------
>
>                 Key: DAFFODIL-2222
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2222
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Performance
>    Affects Versions: 2.4.0
>            Reporter: Michael Miller
>            Priority: Minor
>              Labels: beginner
>             Fix For: 2.6.0
>
>
> 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)