-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: memory in manifest is ignored in favor of cpu #5770
Comments
Hello @chrisschaub. I assume 16g is for all tasks you run in the instance right (and you run 1 task normally)? How often do you see your instance using 16g of ram? I wonder if this is because when you update the service, ECS spins up a new task before deleting the old task. |
I log into each instance with svc exec and saw that 16g. There are two
tasks ... assuming each is a separate container? The container should be
what is provisioned?
…On Fri, Apr 12, 2024 at 2:36 PM Penghao He ***@***.***> wrote:
Hello @chrisschaub <https://github.com/chrisschaub>. I assume 16g is for
all tasks you run in the instance right (and you run 1 task normally)? How
often do you see your instance using 16g of ram? I wonder if this is
because when you update the service, ECS spins up a new task before
deleting the old task.
—
Reply to this email directly, view it on GitHub
<#5770 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZKZMCQFPUHY3SF5YQHAHDY5ASUVAVCNFSM6AAAAABGCNBXY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGI3TEMBTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Christopher Schaub
http://chris.schaub.com
|
that's right. if you have two tasks running then 16g mem makes sense to me since 8g mem is supposed to be per task |
So does it deploy all tasks to one instance?
…On Fri, Apr 12, 2024, 3:26 PM Penghao He ***@***.***> wrote:
that's right. if you have two tasks running then 16g mem makes sense to me
since 8g mem is supposed to be per task
—
Reply to this email directly, view it on GitHub
<#5770 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZKZMHZPAX5SENQOD7X7WDY5AYNXAVCNFSM6AAAAABGCNBXY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGQYDGMBUGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
TLDR not necessarily: https://www.youtube.com/watch?v=Vtymod0nPBo&t=545s. If you use Fargate then the tasks provisioning is all handled by Fargate under the hood and you only pay for the resources you use rather than anything under some specific instance (and the instance is managed by fargate). |
Description:
Specifying a 4cpu 8g memory instance in my manifest
When I exec to the instance, I see 4 cpus and 16g of ram using free -m and htop. It seems like it's using the EC2 standard sizing as a base, not this chart: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-tasks-services.html#fargate-tasks-size .... or is there a soft limit? Even though the container shows 16g, we only have access to 8g. And are paying for 8g? Thanks.
The text was updated successfully, but these errors were encountered: