Skip to content

[Perf] Regressions in System.Tests.Perf_Random #51257

Closed

Description

@DrewScoggins

Run Information

Architecture x64
OS ubuntu 18.04
Baseline 624a8349de1efc4b9504c8d7ba08c2b175d8bb98
Compare ee32ee2240f5771f9cf162695d110c2adccc5107
Diff Diff

Regressions in System.Tests.Perf_Random

Benchmark Baseline Test Test/Base Baseline IR Compare IR IR Ratio Baseline ETL Compare ETL
Next_long_unseeded 5.01 ns 6.05 ns 1.21
Next_long 103.73 ns 110.00 ns 1.06
NextDouble 9.60 ns 11.07 ns 1.15
NextBytes_span 7.54 μs 8.08 μs 1.07

graph
graph
graph
graph
Historical Data in Reporting System

Repro

git clone https://github.com/dotnet/performance.git
python3 .\performance\scripts\benchmarks_ci.py -f netcoreapp5.0 --filter 'System.Tests.Perf_Random*'
Details

Payloads

Baseline
Compare

Histogram

System.Tests.Perf_Random.Next_long_unseeded


System.Tests.Perf_Random.Next_long


System.Tests.Perf_Random.NextBytes_unseeded


System.Tests.Perf_Random.NextDouble


System.Tests.Perf_Random.NextBytes_span


Docs

Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Apr 14, 2021
  2. DrewScoggins commented on Apr 14, 2021

    @DrewScoggins
    MemberAuthor

    Seems related to #50922

  3. removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 12, 2021
  4. modified the milestones: 7.0.0, Future on Jul 12, 2021
  5. dotnet-policy-service commented on Jan 11, 2026

    @dotnet-policy-service
    Contributor

    Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

    This process is part of our issue cleanup automation.

  6. dotnet-policy-service commented on Jan 25, 2026

    @dotnet-policy-service
    Contributor

    This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

  7. removed this from the Future milestone on Jan 25, 2026
  8. locked and limited conversation to collaborators on Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions