It's less about it being not appropriate for perf tests and more so
that you can't directly compare bare metal to a virtual instance. Load
testing virts against virts is fine as long as your factor the drift
in shared resourcing.
Agree that it's not apples to apples, but can't you still get average memory and/or CPU usage? I only suggested it since I thought it would be a cheaper way to run a cursory assessment, which is all I assumed we needed at this point.
This is also why I mentioned gradual rollout and feature flags in my earlier reply. Ideally we can defer establishing performance SLAs until after we're ready to promote this from "experiment" to a first-class stack citizen.
Anyway, on with the experiment! Definitely excited for us to learn more about this as a team (and organization).