Direct answer

An immediate lag increase after installing a plugin can result from startup scans, synchronous event handlers, scheduled tasks or configuration, but correlation alone is not proof.

How to check it

  1. Record the exact newly installed plugin version and the time of its first startup; save logs/latest.log.
  2. Capture /spark profiler start --timeout 120 while the problematic feature runs; examine the plugin method/event branch.
  3. Reproduce the issue on staging with the new plugin enabled and disabled, retaining its dependencies and keeping player workload comparable.

Example: If lag begins only when a plugin opens its GUI for the first time, profile that action; uninstalling all plugins or changing global entity limits would not target the cause.

What to change

Check the plugin’s own profiling, data migration and database configuration. Reduce expensive recurring features if the project documents a supported option, or report a reproducible profile to the maintainer.

Software and version notes

Do not delete an installed plugin’s live data folder or uninstall shared dependencies to perform a quick test. Plugin startup indexing can be temporary and is not necessarily a sustained MSPT problem.

Verify the result

Confirm measured profile cost and player-visible symptoms improve after the isolated change and that affected commands and database writes still work.

References