Voiding items is necessary at various times. For example, Fulgora, producing quality ore, or removing byproducts.
Specifically for this test, we're looking at establishing basic guidelines to allow further exploration of this problem space.
This test may be updated in the future to cover additional designs.
Part 2 will look at more esoteric ways of voiding items, with greater attention on Fulgora for example.
The Test
The test consists of multiple different "building block" ways to void items. Each of these was scaled up to approximately the same voiding rate
Test was ran 1k ticks each, 3 times per map
Scenario
Save
Items voided/minute (each copy)
Items voided/minute (save total)
Image
Infinity chest (control)
infinity.cloned
7200
46,080,000
Recycler shuffle
The classic, insert into two recyclers facing each other
recycler.shuffle.cloned
7200
46,080,000
Recycler with bulk inserter handoff.
Instead of directly inserting, batching the item transfer between the recyclers
The uncommon quality is needed to keep up
recycler.unc.bulk.handoff.cloned
7200
46,080,000
Recycler with legendary stack inserter handoff.
Another variant on the previous, is it better to wait for 16 ready items?
recycler.leg.stack.handoff.cloned
7200
46,080,000
Dumping items into lava
Items take a while to drop into lava, so this is the first (and only) case where 7200/m is not achieved by a single unit
Dumping into lava creates smoke
This has two sub-variants, one that clones in such a way the paste mining drills can see the ore belonging to other rows, and one where they are better spaced and cannot.
lava.cloned.nomineroverlap
~2504
~46,669,552
Landfill recycler shuffle
Instead of going straight to recyclers, go to make landfill first
landfill.recycler.shuffle.cloned
7200
46,080,000
Landfill recycler handoff
Does handoff become better/worse at lower craft rates?
Crafting landfill first was clearly better in all cases. Additionally, adding a handoff is clearly worse than just cross feeding the recyclers.
Having more ore than necessary under an affected miner is harmful for performance. This is mainly a consideration when preparing saves for benchmarking.
Avoid cloning a single ore under a miner, but also avoid having different number of ores available for mining by the different designs.
Region cloner version 3.1.0+ adds intelligence for /autoclone command to improve the default behavior here (manually selected areas can still result in bad behavior).
