projects / platform / upstream / coreclr.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3d5d12d) | patch
Fix bytemark benchmark (#9497)
authorAndy Ayers <andya@microsoft.com>
Mon, 13 Feb 2017 21:34:39 +0000 (13:34 -0800)
committerGitHub <noreply@github.com>
Mon, 13 Feb 2017 21:34:39 +0000 (13:34 -0800)
commit9613ba2e6b6ba47300684c004872fd2fe81573dd
tree453b38e9694de7ee1c7e5a1bc15b119d05c09673tree | snapshot
parent3d5d12d7e897d7c2d90ab83aa4eb95b410cb98f5commit | diff
Fix bytemark benchmark (#9497)

I misunderstood how bytemark uses the `adjust` parameter and inadvertently
enabled self-adjustment for the xunit-perf versions of these tests. Not
surprisingly the results showed crazy run to run variations.

Update these tests to set `adjust = 1` to stop the self-adjustment.

Iteration and loop counts tweaked so that each test runs for roughly
1 second on the perf machines.
tests/src/JIT/Performance/CodeQuality/Bytemark/ByteMark.cs diff | blob | history
Domain: Dotnet / Core;