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

Feed cleaner running out of memory #4266

Open
premun opened this issue Dec 19, 2024 · 0 comments
Open

Feed cleaner running out of memory #4266

premun opened this issue Dec 19, 2024 · 0 comments

Comments

@premun
Copy link
Member

premun commented Dec 19, 2024

Context

It seems like that when we are loading all of the packages and versions into memory at the beginning of the run, we run out of memory.

https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/fbd6122a-9ad3-42e4-976e-bccb82486856/resourceGroups/product-construction-service/providers/Microsoft.App/jobs/feed-cleaner-prod/executionHistory

This didn't happen before the redeployment. But maybe there are too many packages now. It did ran successfully for about a month daily though.

I ran it locally and it ate 6GB while I think there's only 5GB and some available on the container.

Goal

Figure out if we can somehow split the run into several stages so that not all packages need to be loaded into memory.
Or maybe have a look if we can increase RAM on the container job (I don't think we can).

Notes

FeedCleaner can be run locally, though you don't have permissions to clean the feeds. That would have to be given to yourself temporarily via elevation. But it does not matter, the first part when the feed cleaner loads all the package and versions is the one when it hits 6GB in memory whereas the container job only has 5GB.
So it can be tested locally easily - just running the FeedCleaner project. Possibly you need to only allow the FeedCleaner to run locally (by changing appsettings.Development.json).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant