Only subtract ticket wait times for workingMillis when PriorityTicketHolder is used

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2024-03-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The PriorityTicketHolder shifts the contention point of waiting for a ticket to the storage ticketing layer where the curop timer has started. When the SemaphoreTicketHolder is used, the contention point is in the networking layer which is outside of curop timer's tracking.

      We should only consider time waiting for ticket as blocked time when it is also within curop timer's tracking ie. when PriorityTickerHolder is used.

              Assignee:
              Shin Yee Tan
              Reporter:
              Shin Yee Tan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: