Inspector performance monitoring #631
Merged
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.
The Inspector now includes configurable performance monitoring for setter calls, which helps identify potential performance bottlenecks
Performance monitoring settings are part of the
RendererMainSettingsand can be configured via theinspectorOptionsproperty:Settings
Setter Performance Monitoring
enablePerformanceMonitoringbooleantrueexcessiveCallThresholdnumber100resetIntervalnumber5000(5 seconds)Animation Monitoring
enableAnimationMonitoringbooleantruemaxAnimationHistorynumber1000animationStatsIntervalnumber0(disabled)Animation monitor Output
When enabled, you'll see output like this every X seconds:
Warning Output
When the threshold is exceeded, you'll see console warnings like:
This helps identify nodes and properties that might benefit from optimization, such as reducing animation frequency.