better profiler output #5753
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#5753
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?
the output of the profiler is borderline useless a lot of time:
what exactly is e.g.
globalstep[1]
?in #2416 (comment), i mentioned some changes i made to the profiler to show files and line numbers where these things are defined:
much better:
This will help a lot of serverowners and should go to upstream
Not sure should we consider builtin as source/mod upstream or source/engine?
engine, cause upstream is the engine repo and changes only happen on a engine release
sure, why not. it needed a bit more work before it was suitable for upstream though, i was being lazy.
https://github.com/minetest/minetest/pull/14142
upstream got merged, though we'll have to wait until 5.9 for this to go live
maybe i should have left this as "blocked"...
This is one of the issues I'd like to cherrypick into the 5.8.0 engine test