[MC-54806] Red Stone Block and Command Block make process heavier.

I use a lot of Command Block with Fill Clock. When the sum of Red Stone Blocks and Command Blocks are less than 64 in same chunk, there are no chunk update. But when it reach to 64, it happen outbreaks of chunk update. The number of chunk updates are about multiple of 40.

I'm sorry that there are few informations.
These are screen shot multi play and single play.

Linked issues

is duplicated by 1

MC-74599 Fill and setblock clocks cause huge FPS drop Resolved

relates to 1

MC-64791 Fill Clock causes Extreme Network and Chunk Loading Lag Resolved

Attachments

Comments 19

galaxy_2alex 2014-05-08T14:09:56Z

Please provide screenshots that give more information about this issue.

LBPtatuharu 2014-05-08T15:58:36Z

The same problem has occurred.

fienxjox 2014-05-12T20:46:51Z

What are the exact commands in the commandblocks?

LBPtatuharu 2014-05-12T23:32:29Z

In my case.
↑/fill ~ ~-1 ~ ~9 ~-1 ~23 redstone_block 0 replace stone

↓/fill ~ ~1 ~ ~9 ~1 ~23 stone 0 replace redstone_block

Ai Akaishi 2014-05-12T23:59:49Z

I confirmed the same result with the following commands.

/fill ~ ~-1 ~ ~7 ~-1 ~7 redstone_block
/fill ~ ~1 ~ ~7 ~1 ~7 stone

9 more comments

Ai Akaishi 2014-07-15T09:35:51Z

I found Clone Clock also triggered this bug.
The wool colors represent the chunks.
The two command_blocks have the same command, /clone ~ ~1 ~ ~7 ~1 ~7 ~ ~ ~.
The lower command_block clones 63 * air and 1 * command_block every tick, and no redstone_block is cloned.
I think maybe this bug does not depend on the block types.

galaxy_2alex 2014-10-31T21:18:25Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.

onnowhere 2015-03-11T16:38:07Z

Affects current version 1.8.3

marcono1234 2015-03-12T14:17:24Z

Maybe relates to or is duplicated by MC-74599

marcono1234 2015-05-14T13:35:51Z

Confirmed for

1.8.4 might be also rendering related, see http://i.imgur.com/2bBoQ2d.gif

KingSupernova 2016-01-11T20:22:15Z

Can the resolution be changed to "Won't Fix"? I highly doubt that Mojang programed the game with the purpose of it lagging in this way.

Dlawso the Really Lucky Rabbit 2016-01-12T00:10:50Z

Mojang resolving it as intended = 0% chance of changing it to your preferred resolution. Don't act like you don't like the "WAI" resolution. Instead, just leave it for Mojang to discuss.

KingSupernova 2016-01-12T06:01:23Z

@Sonic

First off, that's not true. I have successfully gotten WAI resolutions changed to Won't Fix. Secondly, I'm not sure what you mean by "Don't act like you don't like the "WAI" resolution". I certainly don't like the resolution, that was the point of my comment. Thirdly, there's no need to be rude and imply that I don't know what I am talking about. Indeed, this is not a particularly complex argument, it's simply whether this behavior is intended or not. Intended behavior means exactly that: it was added on purpose. Creepers exploding is intended behavior. Lag on the other hand, is not intended behavior. Mojang did not sit down and discuss how much the game should lag and the best way to implement that lag. It may not be possible to remove the lag, computers have physical limitations. It also may be possible to remove, but would simply require more work than it is worth. In neither case is this intended behavior. It's an unintended problem with the game, that for whatever reason, they will not fix.

Travis Watkins 2016-01-12T12:04:57Z

Doing whole chunk updates after a certain threshold is meant as an optimization. It can be very expensive in bandwidth and CPU to transmit lots of block changes and modify the chunk mesh for them. At a certain point it's cheaper to just resend and rebuild the whole thing.

marcono1234 2016-01-12T16:28:57Z

Apparently this point is badly chosen because it suddenly starts to lag. There is no smoth transition from block updates to chunk updates. Maybe they should consider adjusting the number of block updates required to send a chunk update.

Torabi 2016-01-12T18:37:05Z

Which resolution is chosen for an issue has little to no consequence, which is why we're open to changing them if we think it best reflects the situation. "Works As Intended" and "Won't Fix" both mean "don't expect it to change". The only difference between them is whether Mojang considers the behavior a bug or not.

The lag is not intended, and the resolution of this issue should not be interpreted as such. It's simply an unavoidable consequence of other intended behavior. In this case, WAI means "Can't Fix", whereas "Won't Fix" would imply that it was possible to fix, and they did not want to for some other reason. TANSTAAFL. Computation requires time and memory. If you change a bunch of blocks, that information has to be processed and transmitted. Light and culling have to be recalculated. As @unknown so concisely explained, the current implementation is the most performant solution to the issue that they've been able to design. It may not be the best solution possible, and they may discover a way to improve it in the future, but it's the best they can do at this time.

KingSupernova 2016-01-12T18:48:23Z

@Torabi

I understand that the problem may not be fixable. My complaint in simply with the labelling. The problem with using this method is that there is then no distinction between "can't fix" and "actually intended behavior".

fienxjox 2016-01-12T18:52:11Z

Can I suggest this rather meta discussion be moved to https://www.reddit.com/r/Mojira/ ?

Torabi 2016-01-12T19:10:40Z

How many different resolutions do we need that all essentially mean the same thing? No matter how many we have, they'll never provide sufficient context for all situations, and the more of them we have, the less likely we are to choose the "correct" one. I realize that WAI is often confusing, and perhaps overused, because its usage typically relates to game internals, and not the actual behavior described in the report. How could we improve this? If this is something that matters to the community, then it would be nice to have some discussion on it. However, a single bug report that most people won't see really isn't the place for it. The bug tracker subreddit would be the preferred place to have that discussion.