LockState caching in OperationContextImpl is broken

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.5.3
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • Storage 2016-12-12, Storage 2017-01-23, Storage 2017-02-13
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the OperationContextImpl destructor we create a new locker then immediately destroy it. If the point of caching is that construction/destruction of LockState is too expensive, then we are are still paying the cost and getting nothing out of it. We should consider removing the cache rather than fixing it.

            Assignee:
            Geert Bosch
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: