feat: Exiled Events Profiler #731
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Describe the changes
Implements a Non Overhead Event Profiler to detect plugins causing server lag (CPU spikes) or high memory pressure (RAM allocation/Garbage Collection issues).
What is the current behavior? (You can also link to an open issue here)
Server owners have no builtin way to identify which specific plugin or event handler is causing lag or memory leaks.
What is the new behavior? (if this is a feature change)
The Profiler logs warnings when an event handler exceeds the configured execution time or memory allocation thresholds.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:



Types of changes
Submission checklist
Patches (if there are any changes related to Harmony patches)
Other