Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hive hive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 112
    • Issues 112
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 28
    • Merge requests 28
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • hive
  • hivehive
  • Issues
  • #216
Closed
Open
Created Jan 07, 2022 by Mateusz Żebrak@mzebrakDeveloper

Duplicate measurement during CI replay benchmark

In the CI artifacts - replay benchmark.json file, the measurements array has the first element as the measurement of the last block (5,000,000)

{
  "block_number": 5000000,
  "real_ms": 0,
  "cpu_ms": 0,
  "current_mem": 25958312,
  "peak_mem": 25958312,
  "index_memory_details_cntr": [...]
}

then there are measurements for 100000, 200000.. and again 5000000 block number

{
  "block_number": 5000000,
  "real_ms": 12040,
  "cpu_ms": 12012,
  "current_mem": 25962740,
  "peak_mem": 25964044,
  "index_memory_details_cntr": [...]
}
Assignee
Assign to
Time tracking