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

Activatior issue: The cold start time significantly increases when rw.podsAddressable is set to false. #15477

Open
kinderyj opened this issue Aug 21, 2024 · 2 comments · May be fixed by #15479
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/question Further information is requested

Comments

@kinderyj
Copy link

kinderyj commented Aug 21, 2024

Knative v1.11 on Kubernetes 1.27
Issue Description:
The cold start time significantly increases when rw.podsAddressable is set to false.

The podsAddressable flag is set to false here.

After restarting the Activator pod, the cold start time is quickly as expect. However, after a period of time ( 2 hours or maybe 10 hours), podsAddressable is set to false again, leading to slower cold start times.

For example, we initiate a cold start every 10 minutes:

From 9:00 AM to 12:00 PM: Cold start times are consistently around 800ms.
At 12:01 PM: rw.podsAddressable is set to false by the activator, causing cold start times to increase drastically (e.g., 2000ms, 5000ms, or even 10000ms).

@kinderyj kinderyj added the kind/question Further information is requested label Aug 21, 2024
@kinderyj
Copy link
Author

kinderyj commented Aug 21, 2024

Accourding to #5820 , my cluster does not enabled mesh, and can communicating with the individual pods.

@kinderyj kinderyj changed the title Activatior issue: The cold start time will become slow when rw.podsAddressable is set to false. Activatior issue: The cold start time significantly increases when rw.podsAddressable is set to false. Aug 21, 2024
@kinderyj
Copy link
Author

/kind bug

@knative-prow knative-prow bot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 21, 2024
@kinderyj kinderyj linked a pull request Aug 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant