[Story] Switch to more performance AWS development instance

[tschaffter]

What projects is this story for?

OpenChallenges

As a user, I want

As a developer, I want to have access to enough CPU cores and memory so that I can deploy all the components of the stack.

Description

No response

Acceptance criteria

• The OC stack can be successfully deployed in the dev container with 3-node ES cluster and 3-node Kafka cluster.

Tasks

• [x] Identify a suitable, more performance EC2 instance type for development.
• [x] Switch one development environment to the new instance type and check ACs (Thomas)
• Prepare the t3.2xlarge instance and stop/remove the t3a.xlarge instance.
  • [x] Rong
  • [x] Verena
  • [x] Thomas

Anything else?

No response

Have you linked this story to a GitHub Project?

• [X] I have linked this story to a GitHub Project and set its metadata.

[tschaffter]

T - These types support bursting CPU usage at any time and as long as you need. Each generation has some unique features. In particular, the T4g general-purpose instance type uses AWS Graviton2 processors, which are 40% more efficient than T3 processors. These instances are ideal for web development, testing, and microservices projects.

M - These types of instances are suitable for small and medium-sized databases and enterprise applications like cluster computing and robust data processing.

Fixed vs. Burstable Performance Instances

Burstable performance instances provide a baseline level of CPU performance but let you “burst” above the baseline when your applications need to. Fixed performance instances, on the other hand, let you have consistently high CPU performance.

Small databases, web servers, and developer projects are some of the use cases that need bursts of fast processing but throttle down at other times. Whenever your T instances are idle, they accumulate credits in the CPU, so that when your applications need to burst more than 20% of a core, the CPU can use that credit balance.

For high-volume websites and video encoding, it's best to use the fixed-performance instance types.

Source

Based on what I read, the instance t3.2xlarge would be more suitable than an M instance for web and microservice development.

[tschaffter]

All the members of the team have switched to a t3.2xlarge instance.