-
Notifications
You must be signed in to change notification settings - Fork 33
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
Minimal library that bootstraps #1160
Comments
It'd be possible to break libscope.so into pieces, but I'm not sure we'd get as much benefit as we'd hope. I assume the desire here is to make sure we're being responsible with our resource utilization, even if our library is loaded but not actively producing data. If memory utilization is the primary reason this is being considered, some nuances of linux come into play: If the concern is the linking and loading time... w.r.t. linking time, the recent change toward got-hooking (#1039) should mean that we're not publishing many symbols any more, so the library's effect on linking time should be insignificant. w.r.t. loading, the largest segments of the library would simply be mapped into virtual memory so the load time would be very minimal. If the concern is "unnecessary functionality" that some processes use and others don't... we have a small amount of code to handle technology-specific aspects of processes (go, java), but not enough to offer a meaningful savings if we refactored for this. Almost all of the code to support our two platforms (x86_64 and arm64) is already only built into the appropriate platform-specific build. Code to support TLS encryption isn't always configured to be used, but we've had earlier discussions where we decided not to have dependencies on external libraries if at all possible. |
Also: If the concern is visibility of |
I'm closing this with no action at the current time. |
No description provided.
The text was updated successfully, but these errors were encountered: