Details

    • Epic Name:
      Index Stats
    • Backwards Compatibility:
      Major Change
    • Sprint:
      Query 2.7.8, Quint Iteration 7, QuInt 8 08/28/15, Quint 9 09/18/15

      Description

      It would be useful to be able to get stats from individual indexes about how often they are used. You can see whether a specific query uses certain indexes using explain() but this would allow you to easily see if the index is being used at all. It could just be a simple incrementing counter every time the index gets used.

        Issue Links

          Issues in Epic

            Activity

            Hide
            tpneumat Jeremy added a comment - - edited

            We have system that automatically creates indexes when needed-- this would be especially helpful, allowing us to auto-remove them when no longer used or when underutilized.

            Show
            tpneumat Jeremy added a comment - - edited We have system that automatically creates indexes when needed-- this would be especially helpful, allowing us to auto-remove them when no longer used or when underutilized.
            Hide
            richard.kershaw@corethree.net Richard K. added a comment -

            One more vote for this feature - we have some huge indexes it'd be great to dispose of just as soon as we're 100% sure they're completely unused.

            Show
            richard.kershaw@corethree.net Richard K. added a comment - One more vote for this feature - we have some huge indexes it'd be great to dispose of just as soon as we're 100% sure they're completely unused.
            Hide
            rgpublic rgpublic added a comment -

            "One more thing" I'd like to add: A simple counter would already be a huge step forward, but the date of last access would be even better. Otherwise one would have to compare the values of individual indexes between two dates and find out whether the counter incremented or not. Certainly not that difficult, but while you are at it you might want to consider saving the last access date as well.

            Show
            rgpublic rgpublic added a comment - "One more thing" I'd like to add: A simple counter would already be a huge step forward, but the date of last access would be even better. Otherwise one would have to compare the values of individual indexes between two dates and find out whether the counter incremented or not. Certainly not that difficult, but while you are at it you might want to consider saving the last access date as well.
            Hide
            avivais Avi Vaisenberger added a comment -

            +1 - Should be really really helpful and replace all the hassle going through the profiler docs

            Show
            avivais Avi Vaisenberger added a comment - +1 - Should be really really helpful and replace all the hassle going through the profiler docs
            Hide
            xgen-internal-githook Githook User added a comment -

            Author:

            {u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}

            Message: SERVER-2227 Addition of index usage statistics
            Branch: master
            https://github.com/mongodb/mongo/commit/ae9df7fb11cf359686699aeb9539cb6dc35de675

            Show
            xgen-internal-githook Githook User added a comment - Author: {u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'} Message: SERVER-2227 Addition of index usage statistics Branch: master https://github.com/mongodb/mongo/commit/ae9df7fb11cf359686699aeb9539cb6dc35de675

              People

              • Votes:
                90 Vote for this issue
                Watchers:
                72 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                    Agile