-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
pydrake: Reduce size occupied by modules #10288
Comments
Does not seem unreasonable to me. Backlog? |
Not yet, depending on what solution we want to take for #10408. |
@EricCousineau-TRI could you re-check the object code sizes, now that #10350 has merged? |
All sounds good; knocking down priority to backlog. Will still briefly check sizes, probably tomorrow though. |
If we ever pick this up again, we should try https://github.com/google/bloaty, e.g.,
|
Aside: Running the aforementioned McBloatface on |
Posted a brief benchmark script to run from source, specific to these artifacts. Haven't used McBloatface, yet. Briefly tried using
|
For the record, this is a lot better now that I've been folding modules together. I would advise we finish that first (getting to the point where we only have two shared libraries -- |
At fdd7553, in the
//:install
tree,pydrake
occupies 112MB of space out of 566MB. For comparison,libdrake.so
occupies 26MB.This amount should be reduced, either via #8433 or by reducing the overall module count.
Will increase priority if this starts to become a bottleneck.
EDIT (2019-03-23): Benchmarking stuff:
The text was updated successfully, but these errors were encountered: