The wiki states that placing a container above the hopper doesn't check for floating items to collect. However, this is not the case as when you throw items inside the composter, it is still collected by the hopper below it, despite the composter being defined as a container.
Steps to Reproduce:
Recreate the setup as shown by setup.png, by placing a hopper, then a composter directly above it
Throw an item inside the composter
Observed Results:
The item entity is sucked up by the hopper.
Expected Results:
The item should not get sucked up by the hopper, since the composter is considered as a container. The behavior is expected to be similar to the chest as shown in expected.png, where the item entity is still floating even though it is still within the collection range of the hopper.
Linked issues
Attachments
Comments 3
Mr. K: the composter lag reduction is probably something that works on Java, or it may just be a false theory.
A group of technical Bedrock players actually tested which blocks placed over hoppers most reduce lag. Their data show that a locked (powered) hopper is the least laggy (as expected), and after that any non-container block is equivalent to air. Container blocks actually make hoppers more laggy, presumably because they trigger an extra check. You can view the data here: https://cdn.discordapp.com/attachments/715523208530362389/890030941282631741/Redstone_MSPT_measure.xlsx
Related to MCPE-109449. The composter in particularly is said to be a good way to reduce lag on builds with a lot of hoppers because the check for pulling bone meal is computationally simple. Fixing this would be a great help for sorting and storage systems that use many hopper pipes