8000 PATCH RELEASE Increase API max task to 20 + limit max healthy to 120% by leite08 · Pull Request #3606 · metriport/metriport · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
< 8000 div hidden="hidden" data-view-component="true" class="js-stale-session-flash stale-session-flash flash flash-warn flash-full"> Dismiss alert

PATCH RELEASE Increase API max tas 8000 k to 20 + limit max healthy to 120% #3606

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 3, 2025
Merged

PATCH RELEASE Increase API max task to 20 + limit max healthy to 120% #3606

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions packages/infra/lib/api-stack/api-service.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ function getEnvSpecificSettings(config: EnvConfig): EnvSpecificSettings {
if (isProd(config)) {
return {
desiredTaskCount: 12,
maxTaskCount: 16,
maxTaskCount: 20,
memoryLimitMiB: 4096,
};
}
Expand Down Expand Up @@ -314,6 +314,8 @@ export function createAPIService({
listenerPort,
publicLoadBalancer: false,
idleTimeout: loadBalancerIdleTimeout,
maxHealthyPercent: 120,
minHealthyPercent: 80,
}
);
// https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
Expand Down Expand Up @@ -488,7 +490,7 @@ export function createAPIService({
maxCapacity: maxTaskCount,
});
scaling.scaleOnCpuUtilization("autoscale_cpu", {
targetUtilizationPercent: 80,
targetUtilizationPercent: 60,
Copy link
Member Author
@leite08 leite08 Apr 3, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prob won't make a diff, we prob need to get this down to 20-25% so auto scaling happens, as this is based on the cluster avg... but taking one step at a time

scaleInCooldown: Duration.minutes(2),
scaleOutCooldown: Duration.seconds(30),
});
Expand Down
0