[
https://issues.apache.org/jira/browse/DAFFODIL-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627712#comment-17627712
]
Steve Lawrence commented on DAFFODIL-2400:
------------------------------------------
[~dthompson], do you know if this is the case?
Also of note, the CLI performance command uses a custom ContentHandler (called
DaffodilParseOutputStreamContentHandler) to convert the parsing SAX events to
text. It's possible the measured overhead isn't in the creation of the SAX
events, but is actually in the ContentHandler (which is primarily there just
for testing--users would probably rarely use this). We might want to try using
a "Null" ContentHandler for the SAX API performance command to determine how
much of the overhead is due to that.
> New SAX API causes performance degradations
> -------------------------------------------
>
> Key: DAFFODIL-2400
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2400
> Project: Daffodil
> Issue Type: Improvement
> Components: Performance, SAX
> Reporter: Steve Lawrence
> Priority: Major
>
> The new SAX API caused performance degredations across the board of file
> types. The SAX API is basically just a wrapper around the current API, so
> this is a bit surprising. Need to investigate what is causing these slowdows
> and see if it can be resolved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
