<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h2 class="title">
      <a name="performance-schema-and-plugins">
      </a>
      29.18 Performance Schema and Plugins
     </h2>
    </div>
   </div>
  </div>
  <p>
   Removing a plugin with
   <a class="link" href="uninstall-plugin.html" title="15.7.4.6 UNINSTALL PLUGIN Statement">
    <code class="literal">
     UNINSTALL
      PLUGIN
    </code>
   </a>
   does not affect information already collected for
      code in that plugin. Time spent executing the code while the
      plugin was loaded was still spent even if the plugin is unloaded
      later. The associated event information, including aggregate
      information, remains readable in
   <code class="literal">
    performance_schema
   </code>
   database tables. For
      additional information about the effect of plugin installation and
      removal, see
   <a class="xref" href="performance-schema-status-monitoring.html" title="29.7 Performance Schema Status Monitoring">
    Section 29.7, “Performance Schema Status Monitoring”
   </a>
   .
  </p>
  <p>
   A plugin implementor who instruments plugin code should document
      its instrumentation characteristics to enable those who load the
      plugin to account for its requirements. For example, a third-party
      storage engine should include in its documentation how much memory
      the engine needs for mutex and other instruments.
  </p>
 </div>
 <br/>
</div>
