Information collected for code in a plugin is not affected by removing the plugin with UNINSTALL PLUGIN. Time spent executing code in the plugin was still spent even if the plugin is unloaded later, and the associated event information (including aggregate information) remains readable in performance_schema database tables. For additional information about the effect of plugin installation and removal, see Section 3, “Performance Schema Status Monitoring”.

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.