Maps and Compasses having a far bigger performance impact than reasonable #1213
Labels
No Label
#P1 CRITICAL
#P2: HIGH
#P3: elevated
#P4 priority: medium
#P6: low
#Review
annoying
API
bug
code quality
combat
commands
compatibility
configurability
contribution inside
controls
core feature
creative mode
delayed for engine release
documentation
duplicate
enhancement
environment
gameplay
graphics
ground content conflict
GUI/HUD
help wanted
incomplete feature
invalid / won't fix
items
looking for contributor
mapgen
meta
mineclone2+
Minecraft >= 1.13
Minecraft >= 1.17
missing feature
mobile
mobs
mod support
model needed
multiplayer
Needs adoption
needs discussion
needs engine change
needs more information
needs research
nodes
non-Minecraft feature
non-mob entities
performance
player
possible close
redstone
release notes
schematics
Skyblock
sounds
Testing / Retest
tools
translation
unconfirmed
mcl5
mcla
Media missing
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: VoxeLibre/VoxeLibre#1213
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When looking at some profiling output from my server, the mods with the biggest average performance impact were mobs_mc (24.3%); ?? (28.9%) - i'm mostly sure this one is mcl_mobs because it contains lots of on_step, get_staticdata etc. but fore some reason it does not show that name in profiler, and the weird thing is that mcl_mobs shows up later with 0.1%, which is very unrealistic, it's probably caused by some overrides; mcl_compass (22.4%) and mcl_maps (7.3%). Mobs consuming performance is perfectly fine; but why would something simple as Compasses and Maps take that much (both in a globalstep)? It does not make sense to me, some checking needs to be done. My guess would be that they call other functions that are very performance critical. There is no other explination for compasses taking up almost as much performance as the mob engine or the mobs mod.
Or, similar to mcl_mobs, its called by weird mod interactions and overrides that the profiler can't handle properly.
Created a branch #compass-debug for temporary performance debugging. Do not merge it or use it on your servers, it's just in case someone is interested in helping to fix the problem. (It contains debugging code that should not actually be used in "production")
What about adding a setting to disable these features for now?
The impact on gameplay is realy too big.