Zitadel v4 High memory usage
Hey there folks 👋
Use-case:
I'm currently testing a migration to Zitadel v4.
Environment:
Self-hosted on AWS using ECS Fargate.
Version:
Migrating from Zitadel v3.2.0 to v4.0.0.
Stack:
Zitadel running in ECS Fargate with auto-scaling enabled based on memory utilization.
The ecs task specs are: 0.25 vCPU and 0.5 GB Memory
What you expected to happen:
I expected a smooth upgrade without any significant changes in memory usage or scaling behavior.
What went wrong:
After upgrading to v4.0.0 in my test environment, I noticed ECS Fargate auto-scaling being triggered frequently, spinning up new tasks. Upon checking the metrics, Zitadel was using around 70–80% of the allocated memory, which is significantly higher than before the upgrade.
Attachments:
I’ve attached a screenshot showing memory utilization before and after the migration.
Question:
Has anyone else experienced similar memory usage increases after upgrading to v4.0.0?
4 Replies
Memory usage is high here too. 350 MB or more.
Also it seems zitadel-login 4.0.0/4.0.1 has a memory leak
we have periodic health checks from our load balancer running towards zitadel-login's
/ui/v2/login endpoint
we just changed those to /ui/v2/login/healthy and it's looking better but this is quite worrying, memory isn't freed up on that login endpointopened an issue about it here 🙂 https://github.com/zitadel/zitadel/issues/10562
GitHub
[Bug]: zitadel-login memory leak and zitadel high memory usage · I...
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment Self-hosted Version v4.0.2 Database PostgreSQL Da...
thanks @Ozzzkar lets continue over the issue for this 🙂