Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Consider options to make clr-debuginfo generation faster #92

Open
gtkramer opened this issue Dec 18, 2019 · 4 comments
Open

Consider options to make clr-debuginfo generation faster #92

gtkramer opened this issue Dec 18, 2019 · 4 comments
Labels
performance Reduce time it takes to perform operations

Comments

@gtkramer
Copy link
Contributor

There are one or two find command that become expensive as debuginfo build up over time. If we know the packages from the previous build, we might be able to identify which debuginfo packages have changed and generate debuginfo only for these in a staging directory, and then merge it into the final directory.

@phmccarty
Copy link

The other part to this issue is to implement a debuginfo lifecycle policy so that debuginfo does not "build up over time" quite like it does at the moment. Enacting such a policy would lessen the impact of running the find(1) commands.

@gtkramer gtkramer added the performance Reduce time it takes to perform operations label Dec 19, 2019
@gtkramer
Copy link
Contributor Author

Additionally, as a part of the merging, our syncs would no longer attempt to sync the entire directory, but rather, only place the new files into the existing directories. This would avoid statting every file and folder in the very large directory.

@phmccarty
Copy link

phmccarty commented Jan 8, 2020

Right, there are things we can do to optimize debuginfo generation, and we have work to do to speed up the debuginfo syncs as well. I'm not sure how this will work for aws s3 sync, but wherever rsync is used, we can certainly better tailor those commands for the debuginfo content.

@fenrus75
Copy link

fenrus75 commented Jan 8, 2020 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
performance Reduce time it takes to perform operations
Projects
None yet
Development

No branches or pull requests

3 participants