Two different people on the team running the benchmark at two different locations (the challenges of being remote-first). To be clear, had we prioritized it, we could have built two equivalent systems for this benchmark at one site. However, we are mostly focused on building products, so most of our blog posts end up being someone having a interesting topic to discuss and pulling together data and assets we have on hand or can create quickly for it.

could you perhaps rerun it with one process mlockall()-ing 48GB of RAM, so both end up with 16G usable RAM?