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.

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

Jump to bottom

Immediately scale up from zero in autoscaler #2961

Closed
greghaynes opened this issue Jan 22, 2019 · 4 comments
Closed

Immediately scale up from zero in autoscaler #2961

greghaynes opened this issue Jan 22, 2019 · 4 comments
Assignees
@greghaynes
Labels
area/autoscale kind/bug Categorizes issue or PR as related to a bug.
Milestone
0.4.x

Comments

@greghaynes
Copy link
Contributor

This is the other half of #2659 - When autoscaler gets a stat from the activator, if it is a scale-from-zero case, it should immediately attempt to do so.
@knative-prow-robot knative-prow-robot added area/autoscale kind/bug Categorizes issue or PR as related to a bug. labels Jan 22, 2019
@greghaynes
Copy link
Contributor Author

/assign greghaynes

greghaynes pushed a commit to greghaynes/serving that referenced this issue Jan 23, 2019
Immediately scale up autoscaler for cold-start
4be0da9 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
@greghaynes greghaynes mentioned this issue Jan 23, 2019
Merged
@greghaynes
Copy link
Contributor Author

@josephburnett Can we get this added to milestone 0.4 and the cold-start project?

@mattmoor
Copy link
Member

/milestone 0.4

@knative-prow-robot
Copy link
Contributor

@mattmoor: The provided milestone is not valid for this repository. Milestones in this repository: [Ice Box, Needs Triage, Serving "v1" (ready for production), Serving 0.4]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 0.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@josephburnett josephburnett added this to the Serving 0.4 milestone Jan 28, 2019
greghaynes pushed a commit to greghaynes/serving that referenced this issue Jan 30, 2019
Immediately scale up autoscaler for cold-start
fcaf0c1 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 7, 2019
Immediately scale up autoscaler for cold-start
17e9996 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
000e179 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
9616881 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
b691dff 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
3c4b0df 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
723019a 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
3b777b3 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
greghaynes pushed a commit to greghaynes/serving that referenced this issue Feb 14, 2019
Immediately scale up autoscaler for cold-start
ebc0a58 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes knative#2961
knative-prow-robot pushed a commit that referenced this issue Feb 14, 2019
@greghaynes @knative-prow-robot
Immediately scale up autoscaler for cold-start (#2963)
5b7e155 
When the autoscaler gets a stat to scale a service up from 0 we should
act on this immediately in order to decrease cold-start time.

Closes #2961
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@greghaynes greghaynes

Labels
area/autoscale kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
0.4.x
Development

No branches or pull requests
4 participants
@greghaynes @josephburnett @mattmoor @knative-prow-robot