-
-
Notifications
You must be signed in to change notification settings - Fork 183
Open
Labels
suggestionNew feature or requestNew feature or request
Description
Description
Quite often I'll find profiles like this one No01i25Mgv.zip where datapacks are a significant issue, but, it's not clear which one it is.
By contrast, /perf can tell us this profiling.txt, they're just awful to read.
[04] | | | | scheduledFunctions(84/1) - 30.09%/20.23%
[05] | | | | | function vanilla_refresh:other/clock/5tick(17/0) - 54.53%/11.03%
[06] | | | | | | execute execute as @e[distance=0.0..1.5,predicate=vanilla_refresh:condition/can_show_info,sort=nearest,limit=1] if entity @s[type=!#vanilla_refresh:cannot_show_health,type=!#vanilla_refresh:any_other_mob] run title @p[tag=!1_splatus_actionbar_disabled_2,tag=refresh_spyglass] actionbar [{"translate":"","color": "yellow"},{"selector":"@e[distance=0.1..1.5,predicate=vanilla_refresh:condition/can_show_info,sort=nearest,limit=1]","color": "green"},{"translate": " - ","color": "gray"},{"translate": "❤ ","color":"yellow"},{"score":{"name": "@n[predicate=vanilla_refresh:condition/can_show_info]","objective": "refresh_health"}},{"translate": "/","color": "#bababa"},{"score":{"name": "@n[predicate=vanilla_refresh:condition/can_show_info]","objective": "refresh_maxhealth"},"color": "#bababa"},{"translate": " - ","color": "gray"},{"translate": "Distance: ","color":"#dbdbdb"},{"score":{"name": "distance","objective": "refresh_count"}},{"translate": " blocks away"}](6/0) - 92.82%/10.24%
Proposed Behaviour
Personally, I think it'd be ideal if we could find a way to represent the work per data pack within the regular views, but I can see that being undesirable.
Alternatively, being able to have spark capture and represent these would be a great help at debugging quite common performance pitfalls.
Extra Details
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
suggestionNew feature or requestNew feature or request