Skip to content

Adding Time Hooks for measuring semantics performance #1131

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

Merged
merged 2 commits into from
Aug 9, 2024
Merged

Conversation

Robertorosmaninho
Copy link
Collaborator

This PR introduces hook_timer_start and hook_timer_stop, which can be used to measure the execution time of an instruction or an entire semantics by getting the current timestamp when starting the timer and then when stopping it, we get the current timestamp again, and save the difference into a default file hooks_time.txt in the current directory.

@Robertorosmaninho Robertorosmaninho self-assigned this Aug 8, 2024
@rv-jenkins rv-jenkins changed the base branch from master to develop August 8, 2024 17:38
Copy link
Collaborator

@theo25 theo25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks good but given that I have contributed to this code, don't merge until @dwightguth approves as well.

@dwightguth dwightguth merged commit e098717 into develop Aug 9, 2024
10 checks passed
@dwightguth dwightguth deleted the time-hooks branch August 9, 2024 19:08
rv-jenkins pushed a commit to runtimeverification/k that referenced this pull request Oct 23, 2024
Follow up of
runtimeverification/llvm-backend#1131

This Hook is commonly used to measure VM time in Semantics executions.

The execution of a semantics with `timerStart` and `timerStop` produces
a `hook_time.txt` file with the difference of two timestamps in
nanoseconds.

---------

Co-authored-by: Theodoros Kasampalis <[email protected]>
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.

3 participants