Report nanoseconds for wtperf statistic

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Test wtperf
    • None
    • Storage Engines - Foundations
    • 89.721
    • None
    • None

      It's a part of an initiative of bringing wtperf YCSB closer to MongoDB YCSB (WT-17498). 

      Currently, wtperf reports average read latency in microseconds, while our average read latency is usually under 1 microsecond, making this metric not very useful. We should report it in nanoseconds instead.

            Assignee:
            Ivan Kochin
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: