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

Reduce the impact of the OS clocks on the benchmarks results #1431

Closed
xgreenx opened this issue Oct 19, 2023 · 0 comments · Fixed by #1457
Closed

Reduce the impact of the OS clocks on the benchmarks results #1431

xgreenx opened this issue Oct 19, 2023 · 0 comments · Fixed by #1457
Assignees

Comments

@xgreenx
Copy link
Collaborator

xgreenx commented Oct 19, 2023

Related #948

@xgreenx xgreenx self-assigned this Oct 19, 2023
xgreenx added a commit that referenced this issue Oct 26, 2023
Closes #1431

In the case of super-fast opcodes(< than 1 µs), the `elapse` method is
not accurate enough, which leads to unstable results from benchmarks.

The change aims to stabilize the results from measurements by
subtracting the time required to reset the VM from the total time of the
benchmark.
crypto523 pushed a commit to crypto523/fuel-core that referenced this issue Oct 7, 2024
Closes FuelLabs/fuel-core#1431

In the case of super-fast opcodes(< than 1 µs), the `elapse` method is
not accurate enough, which leads to unstable results from benchmarks.

The change aims to stabilize the results from measurements by
subtracting the time required to reset the VM from the total time of the
benchmark.
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 a pull request may close this issue.

1 participant