Skip to content
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

better auto scaling #10

Open
vincentsarago opened this issue Apr 3, 2020 · 1 comment
Open

better auto scaling #10

vincentsarago opened this issue Apr 3, 2020 · 1 comment

Comments

@vincentsarago
Copy link
Member

Right now the autoscaling is based on the number of requests per ecs task

titiler/stack/app.py

Lines 74 to 81 in 89d8d64

# https://github.com/awslabs/aws-rails-provisioner/blob/263782a4250ca1820082bfb059b163a0f2130d02/lib/aws-rails-provisioner/scaling.rb#L343-L387
scalable_target.scale_on_request_count(
"RequestScaling",
requests_per_target=50,
scale_in_cooldown=core.Duration.seconds(240),
scale_out_cooldown=core.Duration.seconds(30),
target_group=fargate_service.target_group,
)

This should enable fast scaling UP when number of user are loading tiles, but there might be better configuration.

tronto20 pushed a commit to tronto20/titiler that referenced this issue Jan 15, 2024
…-token

JWT logic modified. Token should be sent in parameters.
@AbhishekD15
Copy link

Is there any particular reason autoscaling needs to be based on the number of requests per ecs task ? I am using my own CF template to deploy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants