-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Open
Description
Issue tracker is used for reporting bugs and discussing new features. Please use
stackoverflow for supporting issues.
Expected Behavior
I would not expect this steep increase of memory consumption.
Current Behavior
Soon after it got deployed, ECS memory consumption got increased from 2% to 10%.
A Lamba function with 128mb of memory also failed several invocations.
Might not have enough data points since service deployment has been reverted, but looks like it's also gradually increasing.

Possible Solution
Don't have one.
Steps to Reproduce
Deployed our service which handles high throughput of event streams.
Context (Environment)
go 1.24.5
ECS: ARM64, debian:12-slim
Lambda: x86_64, provided.al2023
Event stream Lambda handlers got behind, backlogs built, ECS memory spike or leak didn't cause a problem since it was reverted.
Detailed Description
Possible Implementation
Metadata
Metadata
Assignees
Labels
No labels