Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Binary analysis cache #240

Open
jrmadsen opened this issue Feb 8, 2023 · 0 comments
Open

Binary analysis cache #240

jrmadsen opened this issue Feb 8, 2023 · 0 comments
Labels
binary instrumentation Binary instrumentation causal profiling Updates to causal profiling capability enhancement New feature or request

Comments

@jrmadsen
Copy link
Collaborator

jrmadsen commented Feb 8, 2023

Binary analysis of ELF files is used in two places: causal profiling and instrumentation. Currently, this step is performed every causal profiling run and every time the omnitrace exe is used but the info is static (unless the file has been modified since the last time it was read). For large applications, this can be time consuming and it is especially tedious when omnitrace-causal is replaying the application numerous times. Proposal is to perform the binary analysis and cache it to a JSON or XML file alongside the file modification timestamp and if the current time is > the modification time, simply read in the cached JSON or XML file.

@jrmadsen jrmadsen added enhancement New feature or request binary instrumentation Binary instrumentation causal profiling Updates to causal profiling capability labels Feb 8, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
binary instrumentation Binary instrumentation causal profiling Updates to causal profiling capability enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant