rework mesecons_debug #1282
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1282
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?
I've rewritten mesecons_debug so that instead of penalties being given based on whether a mapblock exceeds a certain time threshold, instead they are given based on how laggy the server is currently, how much of that lag is due to mesecons, and the relative amount of the total mesecons load that a particular mapblock is generating.
It seems to work decently on a test server, but I'm going to need some help testing it in a more life-like environment, like the test server.
The rewritten version is here:
https://gitea.your-land.de/flux/mesecons_debug/src/branch/yl_stable
testing on the test server went very well. i need to update the documentation, and provide an API for modifying certain constants while the thing is running. then, we can put it on the live server. it might need some adjusting, but it's working exactly as i expected.
This is (more or less) live, closing.