You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2026/03/10 15:26:00 UTC

[jira] [Updated] (DAFFODIL-3070) Investigate non-streaming InfosetWalker

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

Steve Lawrence updated DAFFODIL-3070:
-------------------------------------
    Priority: Minor  (was: Major)

> Investigate non-streaming InfosetWalker
> ---------------------------------------
>
>                 Key: DAFFODIL-3070
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-3070
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Performance
>            Reporter: Steve Lawrence
>            Priority: Minor
>             Fix For: 4.2.0
>
>
> The InfosetWalker walks the internal infoset and converts it to JDOM/XML/etc, and it does so in a streaming-like manner. This streaming can potentially incur overhead.
> We should look into an option that does not trigger the infoset walker at all until the parse is completely (useful for small files), and see if there are any possible optimizations this allows that might reduce the infoset walker overhead.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)