Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-1192

alter mongostat to include 'flushes/s' parameter from db.serverStatus()

    • Type: Icon: New Feature New Feature
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 1.5.3
    • Affects Version/s: 1.5.2
    • Component/s: None

      alter mongostat to include 'flushes/s' parameter from db.serverStatus(). Including the ms timing would be cool, but I think trying to keep the output compact is important, so just putting the # of flushes/sec in there is fine. Generally it would only be 0 or 1. I have a hard time believing the db can do > 1 fsync() per second. But it's still very useful.

      The idea is to provide a column that shows why performance degrades during an fsync(). So when using mongostat and the throughput reduces one can see that "oh, we did a flush, thats why..."

      for example:
      http://pastie.org/990799

            Assignee:
            eliot Eliot Horowitz (Inactive)
            Reporter:
            kgorman Kenny Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: