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

New Comparison View: Make sure we do not use timing values from profiling runs, which may be influenced by profilers. #165

Open
smarr opened this issue Jul 18, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@smarr
Copy link
Owner

smarr commented Jul 18, 2023

With the combining of data from different experiments and trials, there is a risk that we use the data from profiling runs to compute statistics.
But, these might be influence by the profiler, so, it would be better not to use them.

This is possibly an issue since or exacerbated by #164.
It might not be one in practice, depending on how the profiling is set up.
But still worthwhile to verify.

@smarr smarr added the bug Something isn't working label Jul 18, 2023
@smarr smarr moved this from Low priority to Todo in ReBenchDB New Comparison View and No-R Jul 18, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant