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

Reduce InputFileCatalog memory usage #47050

Open
makortel opened this issue Jan 7, 2025 · 4 comments
Open

Reduce InputFileCatalog memory usage #47050

makortel opened this issue Jan 7, 2025 · 4 comments

Comments

@makortel
Copy link
Contributor

makortel commented Jan 7, 2025

In #46975 (comment) it was discovered that InputFileCatalog can take nearly 500 MB memory per stream for premixed pileup files. While #47013 reduces the memory usage by nearly 200 MB per stream, there are further memory optimization opportunities.

Presently the InputFileCatalog does the LFN-to-PFN translation upfront for all LFNs and file locators. This is particularly costly (compared to benefits) for pileup files, where only small fraction of the input files are really accessed by the job. Doing the LFN-to-PFN translation only upon request would allow saving some factors of memory, but we should think a bit of the tradeoffs (mostly if there are any error conditions that would get deferred).

@makortel
Copy link
Contributor Author

makortel commented Jan 7, 2025

assign core

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 7, 2025

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

cmsbuild commented Jan 7, 2025

cms-bot internal usage

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 7, 2025

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

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

2 participants