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

Memory pressure tests #16250

Open
Frassle opened this issue May 22, 2024 · 0 comments
Open

Memory pressure tests #16250

Frassle opened this issue May 22, 2024 · 0 comments
Labels
area/testing kind/engineering Work that is not visible to an external user kind/postmortem-followup Followup item from postmortem

Comments

@Frassle
Copy link
Member

Frassle commented May 22, 2024

There has been instances where subtle changes to code has causes much higher memory usage than expected. Our current tests only catch this in the most egregious cases where CI runners crash out.
We should have tests in place to ensure some large scenarios do not exceed set memory limits.
@Frassle Frassle added area/testing kind/engineering Work that is not visible to an external user kind/postmortem-followup Followup item from postmortem labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/testing kind/engineering Work that is not visible to an external user kind/postmortem-followup Followup item from postmortem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Frassle