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

Highload Documentation #15637

Open
vokhuongcse0604 opened this issue Nov 29, 2024 · 2 comments
Open

Highload Documentation #15637

vokhuongcse0604 opened this issue Nov 29, 2024 · 2 comments
Labels
kind/question Further information is requested lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@vokhuongcse0604
Copy link

Ask your question here:

I have a question about the "High Scale" section in the document Request Flow.
I am confused about the equation "current_demand + target-burst-capacity > (pods * concurrency-target)" being used to represent traffic dropping. I believe the correct equation should be "current_demand < (pods * concurrency-target) + target-burst-capacity" because the incoming traffic (current_demand) must be lower than the setting capacity to route traffic to activator pods. Could you please explain if I am misunderstanding this case?

@vokhuongcse0604 vokhuongcse0604 added the kind/question Further information is requested label Nov 29, 2024
@skonto
Copy link
Contributor

skonto commented Nov 29, 2024

Hi @vokhuongcse0604,

Target burst capacity is a global and per-revision integer setting that determines the size of traffic burst a Knative application can handle without buffering

So that definition means until you have that capacity from the actual application pods, Activator will do the buffering for you (activator will be on the path, proxy mode). If you do have enough pods, you transition to serve mode or high scale.
Please take a look at the related blog post https://knative.dev/blog/articles/demystifying-activator-on-path.

Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Further information is requested lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants