3 ms·
> I’ll build hosts with Terraform (because That’s What We Use These Days) in EC2 > [...] > Create two EC2 instances - their default size is c5.xlarge When yo
by stefantalpalaru 4y ago
> I’ll build hosts with Terraform (because That’s What We Use These Days) in EC2
> [...]
> Create two EC2 instances - their default size is c5.xlarge
When you're benchmarking, you want a stable platform between runs. Virtual private servers don't offer that, because the host's resources are shared between multiple guests, in unpredictable ways.
- zmxz 4y agoWhich platform would you suggest to use for this benchmark?
- stevewatson301 4y agoThe c5 instances get dedicated cores, and thus should be exempt from resource contention due to shared cores.
- speedgoose 4y agoDo you get dedicated IOs on these too? AWS tends to throttle heavily most instances after some time.
- stevewatson301 4y agoFor dedicated disk IOPS you should take a look at the EBS provisioned IO volumes, or perhaps use the ephemeral stores that come with some of their more expensive instances.
- tylerjl 4y agoThis is hard because while, yes, some platform with less potential for jitter and/or noisy neighbors would help eliminate outside influence on the metrics, I think it's also valuable to benchmark these in a scenario that I would assume _most_ operators would run them in, which is a VPS situation and not bare-metal. FWIW, I did try really hard to eliminate some of the contamination in the results that would arise from running in a VPS by doing things like using the _same_ host reconfigured to avoid potential shifts in the underlying hypervisor, etc. But I would certainly agree that, for the utmost accurate results, a bare-metal situation would probably be more accurate than what I have written.