Persistent spikes in CPU and memory usage after scaling Airbyte workers on EC2 instance

Summary

The user is facing persistent spikes in CPU and memory usage on an EC2 instance after scaling up Airbyte workers. They are seeking advice on the most effective solution to address this issue.


Question

Hello Guys,

We’ve deployed Airbyte on an EC2 instance and recently scaled up the number of Airbyte workers using the command ‘docker-compose up --scale worker=3 -d’. However, after upgrading our server to vertically with double and even quadruple its capacity, we’re still experiencing persistent spikes in CPU and memory usage. What would be the most effective solution to address this issue?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["airbyte-platform", "ec2-instance", "scaling", "cpu-usage", "memory-usage", "docker-compose"]