Optimize resource restart/stop performance #4421
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MohabCodeX
changed the title
FileEX
requested changes
Sep 5, 2025
MohabCodeX
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem: as explained in #864 .
Performance Results:
tested with resources containing 1,681+ elements across multiple restart cycles. Consistent results show elimination of client-side frame drops and server-side efficiency improvements.
Client Performance Improvement:
• Before: Min FPS dropped to 13.06 during restarts (458% performance loss)
• After: Min FPS maintained at 72.70+ (rock solid performance)
• Frame drops: Eliminated completely (2 → 0 drops detected)
• Player experience: "POOR" → "EXCELLENT" (smooth gameplay maintained)
Server Efficiency:
• CPU usage: Reduced from 20.79% to 9-12% average (more efficient processing)
• Memory usage: 40% reduction in peak memory consumption
• Restart time: Consistently instant (0ms) operations
• Network load: Eliminated packet flooding entirely
For further assurance, it can be tested and verified by someone else, that would be highly appreciated.
Backward Compatible ✅👍🏻