Skip to content

Conversation

@Essoz
Copy link
Collaborator

@Essoz Essoz commented Jan 10, 2025

This PR adds fine-grained instrumentation at the invariant deployment stage.

Given the list of invariants, mldaikon.collect_trace should be able to choose variable and API instrumentation methods based on information requested by the invariants. It will help achieve minimum overhead at checking stage.

@Essoz Essoz self-assigned this Jan 10, 2025
@Essoz Essoz changed the title Finegrained Instrumentation Options Fine-grained Instrumentation Options Jan 10, 2025
@Essoz Essoz force-pushed the per_API_customizable_instrumentation branch from b38e400 to 489bec9 Compare January 11, 2025 04:48
@Essoz Essoz force-pushed the per_API_customizable_instrumentation branch from 2a4c2cb to be233bb Compare January 11, 2025 16:42
@Essoz Essoz force-pushed the per_API_customizable_instrumentation branch from 5c6ba54 to 0c4460c Compare January 12, 2025 02:47
@Essoz
Copy link
Collaborator Author

Essoz commented Jan 12, 2025

With option to enable/disable dumping for args/return values, the overhead already matches the paper on my workstation.
Currently the overhead for deploying 100 invariants on transformer and resnet18 is near 0.

Probably no need to implement fine-grained selective dumping on individual argument due to its excessive complexity. Delaying this for further experiment if overhead needs to be lowered further.

@Essoz Essoz merged commit 8c29d6d into main Jan 12, 2025
2 checks passed
@Essoz Essoz deleted the per_API_customizable_instrumentation branch April 30, 2025 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants