Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Allen Allen
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 183
    • Issues 183
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 52
    • Merge requests 52
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCb
  • AllenAllen
  • Merge requests
  • !595

WIP: Allen running configuration modes

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Dorothea Vom Bruch requested to merge dovombru_throughput_mode into master Jun 28, 2021
  • Overview 0
  • Commits 180
  • Pipelines 37
  • Changes 40
  • Add program option mode to select how the input is passed to the thread-stream pairs:
    • benchmark: should be as reproducible as possible, and should distribute an equal amount of work to each thread/stream. Each thread/stream should run a total of events-per-slice * repetitions events. All thread/streams runs on the same events.
    • throughput: is meant for representative throughput measurements across significative portions of data samples. It should be used only with MEP or MDF input. In total events-per-slice * number-of-slices * repetitions events are processed. This should be independent of the number of thread-stream pairs.
    • datataking: continuous mode is the actual data taking mode. The program is run indefinitely.
    • MC-Check: A configurable number of events is processed, w/o repetitions.
  • Remove non-stop option (now datataking mode)

The throughput mode is a new feature, which enables throughput measurements across larger sets of events. Until now, we measured throughput only in benchmark style, where the same events are passed to all thread-stream pairs. throughput mode on the other hand loads a configurable number of events and passes different chunks of events to different thread-stream pairs.

Closes #248 #130

Based on !561 (merged)

Marked as WIP until a CI test is added for the throughput mode.

Edited Sep 07, 2021 by Dorothea Vom Bruch
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: dovombru_throughput_mode