CyclopsMC / IntegratedDynamics / 34055376421

47%

master-1.21-lts: 47%

push

github

Add ingredient index benchmarks for collision-heavy and plain storage shapes

The existing benchmarks spread instances over every registered item, adding
component variants only once the item list is exhausted. One shape, and a
middling one: collision chains stay short enough to hide the shapes that hurt,
and it carries enough components to hide the shape that dominates real storages.

Five shapes now exist:

* SPREAD, as before, so existing result history stays comparable.
* SINGLE_ITEM: every instance on one item, distinct only by components. A
  storage full of enchanted books, damaged tools or written books.
* FEW_ITEMS: spread over 50 item types with component variants within each.
* HEAVY_COMPONENTS: each stack carries lore and container contents, so the cost
  of hashing a component map is visible. This guards the opposite risk, a hash
  that is more discriminating but more expensive.
* PLAIN: distinct by item and count only, so no stack carries a component patch.
  This is what a large modpack storage mostly looks like.
* MIXED: one instance in ten carries a component. PLAIN and SPREAD bracket a
  real storage network rather than describing one; this sits between them.

Item-only lookups also only had a benchmark on the spread shape, although the
number of variants of one item is what decides their cost. They are now covered
on the plain, mixed and single-item shapes too.

Air is now excluded from the item pool. A stack of it is empty and carries no
components, so a fixture entry built on it indexes nothing, which makes a
single-item shape index nothing at all.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mxjin31W1Lmq5XK1CCe84v

3076 of 9260 branches covered (33.22%)

Branch coverage included in aggregate %.

12938 of 24821 relevant lines covered (52.13%)

2.49 hits per line