flux reports: keep your machines simple. lim ... #3093
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#3093
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?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
the idea here was to limit the # of actions per mapblock, not the amount of time they take.
I don't like this idea. The only reasons machines need limitation is because of lag. If they arent laggy, there is no reason to slow them down. This would only be annoying.
machines are one of the major generators of lag currently, which is why they need limitation. currently, mesecons_debug penalizes mesecons on how they affect the server globally. i think it'd be a better idea to limit the amount of computation locally against mapblocks. this would naturally limit them globally because players can only keep a small number of mapblocks loaded.
Question. If this was implented, how many actions/sec would be allowed for one mapblock?
we'd have to test to figure out what a good limit is.
And what exactly would define an "action"?
this would also have to be fleshed out.
also, note that this change is unlikely to be worked on anytime soon, i'm busy w/ a lot of other big projects. but i did want to make a note to consider this approach when i get back creating a job-scheduling framework for minetest.
I think the current one is just fine and this one would just be more annoying.