Skip to content

Consider loading shared libraries concurrently with module construction #48169

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

Open
Dr15Jones opened this issue May 25, 2025 · 4 comments
Open

Comments

@Dr15Jones
Copy link
Contributor

As we are constructing one module we could concurrently start loading the shared library needed for the next module. The linux shared library system already prevents concurrent loading of shared libraries and some module's constructors are not thread safe so it would likely take a lot of effort to concurrently construct modules. Pipelining the shared library loading and module construction would have the lowest risk of a concurrency problem while still giving some startup benefit.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 25, 2025

cms-bot internal usage

@cmsbuild
Copy link
Contributor

A new Issue was created by @Dr15Jones.

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

cms-bot commands are listed here

@Dr15Jones
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

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