3 ms·

There's a few SaaS/normal software out there that capitalize on the per chassis/compute unit performance difference amongst identical SKUs. My employer runs a

There's a few SaaS/normal software out there that capitalize on the per chassis/compute unit performance difference amongst identical SKUs. My employer runs a few HPC grid workloads on AWS and Azure and these softwares would benchmark the instances on boot and drop the ones that were below a certain threshold, and we'd keep spawning instances until the fleet was up past our threshold. (Ultimately, we didn't buy the software). I wondered (not too hard) why there could be such a difference in performance, but your comment has given some good insight into that.

judge2020 7y ago
don't think this would work on GCP since they regularly preform 'live migrations' https://cloud.google.com/compute/docs/instances/live-migration https://cloud.google.com/compute/docs/instances/live-migrati...
- eru 7y ago
  I think they don't live-migrate pre-emptible instances: https://cloud.google.com/compute/docs/instances/live-migration#preemptiblemaintenance https://cloud.google.com/compute/docs/instances/live-migrati...
  - dilyevsky 7y ago
    They just preempt them when they need to migrate.
    - eru 7y ago
      Yes. So at least you explicitly know when you are getting new physical computers, so you can run your selection process again.
praptak 7y ago
This particular solution doesn't sound feasible in the long term. If a significant portion of customers start using this, the benefit is nullified. And providers will probably react. It's very similar to the "download boosters" of old which worked until they got popular which is when download sites started throttling.