Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-224

plugin usage numbers in the feedback reports

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 5.5.24
    • Component/s: None
    • Labels:
      None

      Description

      We want to see what plugins are used and what aren't. To profile this, we need plugin usage numbers in the feedback plugin reports.

      An easy way to get a number that approximately corresponds to how often a plugin was used would be to count how many times a plugin was locked.

      Adding it to I_S.FEEDBACK table reveals another problem. Currently it reports plugin versions as, say,

      ...
      | Xxx | 1.2 |
      ...
      

      for plugin "Xxx". To report usage counters we'll add another row like

      ...
      | Xxx used | 1234 |
      ...
      

      with the space in the name, to avoid possible clashes with anything from the show status or show variables.

      For consistency, we'll report versions as

      ...
      | Xxx version | 1.2 |
      ...
      

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            serg Sergei Golubchik added a comment -

            pushed.

            took longer than expected because of collateral bugfixes (failed plugins not properly disabled, I_S plugins weren't locked at all, xtradb-plugin failed tests)

            Show
            serg Sergei Golubchik added a comment - pushed. took longer than expected because of collateral bugfixes (failed plugins not properly disabled, I_S plugins weren't locked at all, xtradb-plugin failed tests)

              People

              • Assignee:
                serg Sergei Golubchik
                Reporter:
                serg Sergei Golubchik
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Time Spent - 6 hours Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - 6 hours Remaining Estimate - 2 hours
                  6h