What EC2 instance sizes does Galaxy use?


What EC2 instance sizes does Galaxy use?

Also, interested in understanding where the 0.5 - 4 ECU numbers come from.


Q: What is an “EC2 Compute Unit” and why did you introduce it?

Transitioning to a utility computing model fundamentally changes how developers have been trained to think about CPU resources. Instead of purchasing or leasing a particular processor to use for several months or years, you are renting capacity by the hour. Because Amazon EC2 is built on commodity hardware, over time there may be several different types of physical hardware underlying EC2 instances. Our goal is to provide a consistent amount of CPU capacity no matter what the actual underlying hardware.
Amazon EC2 uses a variety of measures to provide each instance with a consistent and predictable amount of CPU capacity. In order to make it easy for developers to compare CPU capacity between different instance types, we have defined an Amazon EC2 Compute Unit. The amount of CPU that is allocated to a particular instance is expressed in terms of these EC2 Compute Units. We use several benchmarks and tests to manage the consistency and predictability of the performance from an EC2 Compute Unit. The EC2 Compute Unit (ECU) provides the relative measure of the integer processing power of an Amazon EC2 instance. Over time, we may add or substitute measures that go into the definition of an EC2 Compute Unit, if we find metrics that will give you a clearer picture of compute capacity.


He’s asking about the instances that run the docker containers on Meteor Galaxy. Not the generic AWS ec2 information…


actually OP asked two questions, 1) what size instance does Galaxy use, and 2) where does the ECU number come from. I answered #2


Yeah. Does anyone know which ec2 instances they use? Don’t see any 4 ecu units on aws for example


Galaxy is built on top of kubernetes, so there’s no real direct correlation between the underlying server instances and the containers that run on top of it from an ecu standpoint.

You could look at it like this: They could be running clusters of m4.16xlarge instances, their resources are pooled in kubernetes. They then run containers with certain restrictions that resemble ecu’s. So a single 16xlarge instance could be running like 16 4-ECU galaxy containers for example.

In other words, they are not running containers directly on top of ec2 instances, but pooling multiple ec2 instances into a large resource pool on which they run containers. The underlying instance type doesn’t matter as long as it’s large enough that a single instance can support their largest container offering. In this case the minimum instance type would be xlarge.