Redstone hoppers and devices causing major fps drop

I too experience the issue I'm on a I'd say quite a decent computer yet, I'm experiencing major fps drops when droppers move items, my creation is around 5x5x3, yet I still get terrible fps drops around 30-40 fps drops.

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.

Still an issue in the current patch. Please figure out how to get this fixed. The only thing that helps this is optifine, which is not a part of minecraft and I should not have to rely on to a third party mod to be able to use redstone droppers and hoppers inside of mojang's own game.

has there been any update to this issue?

no resolution to this bug for 3 months, but let's go ahead and release another patch to the game. Good work mojang.

So you're saying they should stop all work on all other bugs or features until they solve this one issue that relatively few people seem to be experiencing, considering the single vote on this issue, and no other duplicate reports?

Also, how would they fix this issue without releasing another patch? Time travel?

https://mojang.atlassian.net/browse/MC-14983
another bug with hoppers, could be related, but not the exact same one. In since April.

Not saying they should drop everything, but clearly they haven'y since there have been 4 patches to the game since the one I've linked is reported.

And by patch I was referring to the update 1.7.

As far as single votes, I'm happy to see bugs reported and given lots of info get taken so seriously with even just one vote.

How does the confirmation process work then, I need 10 people to agree with it before it gets "confirmed"

You and I can debate point after point about all of this, but my main point remains. For this one there has been nothing done for 3 months, and I have watched and waited on this one.
I have also watched the other thread for the past 3 months, and it hasn't had any resolution for 5 months even though there are 6 voters and 7 people watching the issue, and yet we're going to get new biomes, but not fixes to things currently ingame causing "some" people issues.

If you want to tell me a logical reason that mojang can implement new biomes, etc while not fixing current issues ingame, then I will be happy to listen. (besides the fact that they can do whatever they want, which I know, but that doesn't mean I have to be happy about it obviously)

If all you are going to do is berate me for posting a factual statement (if a little heated because it's frustrating to see a bug report sit for 3 months and another for 5 months while new things get added) then just mark it as still occurring please and I'll get back to waiting for an update on the bug that hasn't come.

Confirmation status depends upon a moderator (which you have correctly ascertained that I am not) successfully reproducing the problem, or a significant number of other users reporting that they experience the issue. How can a developer solve a problem if they can't even see it for themselves? How are they to know what causes the problem, how to fix it, or if what they're trying has any effect, unless they can reproduce it themselves? Otherwise it's just a big guessing game. And the problem might not even exist in their code. The best they can do is hope it gets fixed on accident, as a result of some other change, or during a major refactor like the one the Minecraft codebase is going through right now.

Different people place different amounts of importance on which bugs should be higher priority than others. This is reflected in the voting system, and helps Mojang gauge which bugs to focus on fixing. However, how much time and effort a bug takes to fix is also a factor, as well as whether or not they have any idea where to start. Writing code is not just a mechanical process; it's also a creative, artistic one. Fixing bugs isn't the same as digging ditches.

Some people place more importance on the development of new features than on fixing bugs, whether because they don't encounter those bugs, or don't feel their experience is seriously impacted. While there isn't a formal voting process to prioritize feature development (other than perhaps the rating systems on the suggestions forum and subreddit), the desire, by players, for new features is surely worthy of some consideration, just like their desire for bugs to be fixed.

They have fixed bugs, with each of the updates they've released. They just haven't fixed this bug. And there are thousands more, all demanding their attention. Try as they might, Mojang is only about 40 people (and some of them don't even work on the PC version of Minecraft), while they have more than 12 million customers. How can anyone be expected to provide perfect, prompt service to that many people, when so many of them are asking for different things? Can you make 300,000 different people who want different things all happy, all at once?

You, as the reporter, should be able to edit the issue and update the Affect Version/s list yourself. There is no need to wait for a mod to do so.

That is a much more comprehensive statement, thank you for taking the time to type it out. As mentioned, I did in fact read it and agree with all of your points. But as I said as well it doesn't mean I'm happy about it, nor does it mean I can't voice my frustration.

Thank you for actually taking the time to prove you aren't just a troll and I do appreciate honest, open discussion. Good Luck with what you do!

Alright, I did some testing. I put the schematic in a world, and can confirm that certain parts of the process have a significant effect on FPS, on 13w37b. I normally get 60FPS, but while items are being sorted, my FPS drops down to 10-25. However, I have the same problems using this sorter in 1.5.2, except I have higher FPS to start with (~85) and it only drops down to about 40.

This only occurs while items are moving through certain parts of the machine. Specifically, the hoppers with comparators. According to the debug screen, the culprit is "root.gameRenderer.level.updatechunks.sort".

Large quantities of hoppers by themselves don't seem to cause me any trouble, unlike MC-14983. I built a solid block of them, 8x5x11, threw items in the top ones, with no hit to performance. I also made a large winding loop of hoppers feeding into each other, once again, with no performance problems. if I replicate just the hopper/comparator/chest section, that causes some performance degradation, but only about 10FPS.

I then tried knocking off large portions of the sorter. The more sections I removed, the less the FPS dropped while it was running. With only 1/4 of the sorter, my FPS only dropped to 45.

Not really sure what's causing this. Maybe lighting updates from the repeaters and torches. Maybe redstone updates. Maybe the comparators. I think Mojang's simply going to have to run a profiler on it while it's running. I'll attach a world with just the sorter in it to make it easier to test. Regardless, the issue was there in 1.5.2, it's only made more apparent by the general loss of FPS in 1.6.

@unknown, I suggest you update the Affects Version/s field to include the latest snapshot, so that it will show up in searches for current issues.

updated, thank you for testing.

Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.7 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Also is the hopper/comparator in the 12x12 always-loaded chunks? Does the lag happen at the 12x12 chunk line? Its sounding like this one relates to or is a duplicate of MC-42373 which has been confirmed.

I would agree that when activating the device, the redstone clock that carries the items up is the part causing the issue and would be the main cause of this issue, yes. That would be a duplicate of mine, or vice versa, I'm not picky. lol.

It would be really interesting if someone could test something like this with the lighting update routines disabled, much like MC-32933. That would really help narrow down whether this is a lighting update issue, or something internal to comparators or redstone.

I found the lag to be most significant when the items were travelling down, rather than up. There's a lot going on there, with the comparators, hoppers, and other redstone being toggled very rapidly as it limits the throughput of the items to ensure that the hoppers remain almost full of a particular item so they can be used to filter and sort. It may be overlapping calls, with a process not being completed before the state changes and the process is called again, constantly being interrupted.