Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • Merge requests
  • !378

make sleep semaphore threshold configurable

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Florian Fischer requested to merge configure-sleep-sem-threhold into master Apr 24, 2022
  • Overview 3
  • Commits 1
  • Pipelines 1
  • Changes 3

I think we rashly merged !377 (merged). Mazstab using the xs problem size reports that using the semaphore greedy (EMPER threshold == 0) has significant (at least how interpret the plots no idea about the actual statistics) benefits for 5 out of 7 benchmarks.

matmul.pdf for example.

I don't trust those reasults because my rts-descriptor also uses sleep_sem_threshold=workerCount which should exactly be exactly the same as the default configuration.

emper:
 meson:
   options:
     sleep_sem_threshold: workerCount
Edited Apr 24, 2022 by Florian Fischer
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: configure-sleep-sem-threhold