Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2867

Optimize Timestamp varint decoding

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

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 1.11.0
    • None
    • None

    Description

      In looking at a profile with some delta reads, I noticed ~11% of CPU going to GetMemcmpableVarint, much of which is from Timestamp decoding. In practice, any timestamp from HybridClock will need an 8-byte varint, so we can fast-path that case. (unfortunately it's too much effort to change the data format to not use a varint here)

      Attachments

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

          People

            tlipcon Todd Lipcon
            tlipcon Todd Lipcon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment