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

MaxMemoryPreload monitoring shows noticeable increase when large number of packages are rebuilt #46359

Open
makortel opened this issue Oct 11, 2024 · 7 comments

Comments

@makortel
Copy link
Contributor

Observed in #46200 (comment).

@makortel
Copy link
Contributor Author

assign core

@cmsbuild
Copy link
Contributor

New categories assigned: core

@Dr15Jones,@makortel,@smuzaffar you have been requested to review this Pull request/Issue and eventually sign? Thanks

@cmsbuild
Copy link
Contributor

cms-bot internal usage

@cmsbuild
Copy link
Contributor

A new Issue was created by @makortel.

@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@makortel
Copy link
Contributor Author

Here is an example from #46204 (comment)
image

@makortel
Copy link
Contributor Author

With @Dr15Jones we hypothesized maybe the FileInPath could lead to this increase?

@Dr15Jones
Copy link
Contributor

Another reason could be the PluginManager cache would also include reading from the workspace's lib directory and therefore increase its working memory.

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

3 participants