Skip to content
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

Add tracing for expensive operations #314

Open
hackaugusto opened this issue May 7, 2024 · 0 comments
Open

Add tracing for expensive operations #314

hackaugusto opened this issue May 7, 2024 · 0 comments

Comments

@hackaugusto
Copy link
Contributor

Some operations are inherently slow, like key generation. It is useful to know how much time these take. It would be useful to add tracing annotations to some of these operations.

The current motivation for the above is the miden-base tests, there we do key generation, and it is unclear how much time the test execution is part of the keygen, and the test itself. Having a bit more of insight on that would help decide when to mock / hard code a test key. (Ofcourse, this very example doesn't need tracing in crypto and can be done by hand, this is the motivating example, I think this would be useful in general).

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

No branches or pull requests

1 participant