You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2024/09/30 14:19:00 UTC

[jira] [Commented] (DAFFODIL-2935) EXI output from parse should be faster than textual XML

    [ https://issues.apache.org/jira/browse/DAFFODIL-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885919#comment-17885919 ] 

Mike Beckerle commented on DAFFODIL-2935:
-----------------------------------------

I edited the subject to drop "input", as I don't believe we have measurements related to unparsing. 

> EXI output from parse should be faster than textual XML
> -------------------------------------------------------
>
>                 Key: DAFFODIL-2935
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2935
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Back End
>    Affects Versions: 3.9.0
>            Reporter: Mike Beckerle
>            Priority: Major
>
> Recent performance work showed that EXI, while creating smaller output sizes, is not faster. 
> This seems to have something to do with using the SAX API.
> Daffodil *should* be able to pass the same element name objects (exact same object reference) repeatedly to the start-element and end-element SAX events. These strings are stored in the element ERD data structure and should not need to be allocated/constructed or even traversed for each element. (If we're not storing the exact right string on the ERD, it should be added so it's sitting there ready to use.)
> We also don't know if Exificient library is able to take advantage of the fact that every start-element and end-element event for the same element should be passed the exact same object reference for the string identifier(s) of the element. 
>  



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