Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E emper
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • i4i4
  • manycore
  • emper
  • Issues
  • #15
Closed
Open
Issue created Mar 24, 2021 by Florian Schmaus@flowOwner

Consider using "Fast Random Integer Generation in an Interval" Lemir (2019), e.g. for random victim selection when stealing work

Right now, EMPER's random victim selection is even biased, due https://gitlab.cs.fau.de/i4/manycore/emper/-/blob/33cad423220b3fc3c4a0f0202a61d45d104b0a19/emper/strategies/AbstractWorkStealingScheduler.cpp#L71

  • https://arxiv.org/abs/1805.10941
  • https://dl.acm.org/doi/10.1145/3230636
Assignee
Assign to
Time tracking