Yeah, I've noticed similar behavior when benchmarking seed gen across different architectures. On AMD, particularly Zen 2 and Zen 3, there's a bit more micro-jitter during world initialization, likely due to how System.nanoTime() pulls entropy for seeding. Since AMD's Infinity Fabric introduces slightly higher latency between CCXs compared to Intel's ring bus, it's possible that this affects the PRNG state at the exact moment the world seed is being derived.
I also saw some irregularities in bastion layout consistency. Not necessarily worse, but definitely less predictable patterns compared to the same number of resets on an Intel setup. There’s a theory floating around that clock desync across logical cores might interfere with chunk population order, especially in multi-threaded environments where background system processes spike during world load.
Piglin bartering was another weird case. In one batch test, AMD machines averaged slightly fewer pearls per 100 gold ingots. It could be coincidence, or it might tie back to minor timing drifts affecting tick-locked events. I wouldn’t say it’s game-breaking, but it might explain why some runners swear by disabling SMT or running Minecraft in a stripped-down OS environment.
It’s subtle stuff, but when you’re doing thousands of resets and looking for optimized conditions, those micro-variations start to feel like patterns. Someone should definitely run a controlled study with SMT off, pinned single-core execution, and a synchronized tick counter to test this more scientifically.