Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DAFFODIL-1775

Performance - Investigate avoiding compiling non-expressions

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • None
    • 2.0.0
    • None
    • None

    Description

      Many properties are allowed to be DFDL expressions, but expressions are not required (e.g. dfdl:initiator, dfdl:separator). Even when these expression are provided as a constant (e.g. dfdl:inititor="foo"), we still compile them. Sometimes this is necessary for things that are numeric so that we can convert the constant string into a numeric constant. However, if the property results in a string, there really is no need to compile it into a string. Avoiding this would prevent allocating DFDLPathExpressionCompiler's and parsing/compiling a value, only to return a Constant of the same value. ��As DFDL-1774 mentions, expression compilation is very slow, so if we could avoid this, it may improve performance.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dfthompson Dave Thompson
            slawrence Steve Lawrence
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 0.4h
                0.4h

                Slack

                  Issue deployment