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

Gradually increase LFC quota without taking working set into consideration #871

Open
stradig opened this issue Mar 22, 2024 · 4 comments
Open
Assignees
Labels
a/performance Area: relates to performance of the system c/cloud/compute Component: cloud: compute

Comments

@stradig
Copy link
Contributor

stradig commented Mar 22, 2024

To improve performance of autoscaled computes @Bodobolero's tests showed that the LFC quota can be a deciding factor for the performance. As an experiment we want to gradually increase the LFC quote and see what benefits we are getting from that and in what kinds of problems we are running into.

@Bodobolero Bodobolero added a/performance Area: relates to performance of the system c/cloud/compute Component: cloud: compute labels Mar 22, 2024
@skyzh
Copy link
Member

skyzh commented Mar 25, 2024

ref issue on the compute side neondatabase/neon#6919

@stradig
Copy link
Contributor Author

stradig commented May 6, 2024

@skyzh Is this finished or are you planning further changes?

@skyzh
Copy link
Member

skyzh commented May 6, 2024

Planning on remove the limit on vm-builder. Plan to do it after the swap config change gets released so that the disk usage metrics can be observed without interference of other factors.

@skyzh
Copy link
Member

skyzh commented Jun 17, 2024

vm-monitor changes: neondatabase/neon#8066

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/performance Area: relates to performance of the system c/cloud/compute Component: cloud: compute
Projects
None yet
Development

No branches or pull requests

3 participants