Airbyte 0.63.13 - High CPU Usage & docker-proxy Overload Even Without Other Projects #59701
Unanswered
pavankalyan-soulpage
asked this question in
Deployment
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Airbyte team,
I'm running Airbyte version 0.63.13 via Docker, and I'm experiencing severe performance issues even without running any other projects on the VM.
Issue Summary:
The CPU usage spikes to 100% shortly after startup
Many docker-proxy processes are spawned (over 20)
The load average remains high (>5.0) even when idle
No other workloads (like DFlux) are running — only Airbyte
VS Code Server is occasionally used but not the root cause
VM Environment:
OS: Ubuntu 24.04
vCPUs: 4
RAM: 16 GB
Disk: 125 GB SSD
Docker Version: 27.2.0
Airbyte Version: 0.63.13
Deployment: Docker (not Kubernetes)
Troubleshooting Done:
Checked logs from airbyte-server, airbyte-worker, airbyte-temporal, and airbyte-proxy — no clear error messages
Confirmed that even basic sync jobs or idle time causes high CPU
Confirmed that .vscode-server is not the culprit
Cleaned up old containers, images, and volumes
Static ports are defined in docker-compose to avoid random port binding
Request:
Is this a known performance issue in Airbyte 0.63.13?
Is my VM underpowered, or is there a way to tune Airbyte for low-resource environments?
Any recommended flags/configs to reduce CPU load (e.g., Temporal tuning, worker limits)?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions