Uploaded image for project: 'Apache AsterixDB'
  1. Apache AsterixDB
  2. ASTERIXDB-3477

Summarized profile shouldn't compare build and probe times when computing min/max time.

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.9.9
    • 0.9.10
    • RT - Runtime

    Description

      The summary profile in the plan right now doesn't differentiate between the build and probe sides of the join when computing the min and max time taken. This is misleading because in many cases the build will take far less time, and therefore there will be a wide range between min and max time even if all probes and builds take roughly the same amount of time respectively. This leads to a false appearance of some sort of skew or other performance problem when the behavior is normal and expected. 

      Attachments

        Activity

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

          People

            imaxon Ian Maxon
            imaxon Ian Maxon

            Dates

              Created:
              Updated:

              Slack

                Issue deployment