Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
margo
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • sds
  • margo
  • Issues
  • #53

Closed
Open
Opened Oct 18, 2019 by Philip Carns@carns
  • Report abuse
  • New issue
Report abuse New issue

sparkline_data_collection_fn() using ABT_thread_yield() instead of margo_thread_sleep()

Low priority to come back to this later. The ULT that runs sparkline data collection needs to idle most of the time, which seems like a sensible use of margo_thread_sleep(). There is a bug that prevents that from working correctly that we need to dig into.

Right now the code is using ABT_thread_yield() instead, which could result in the sparkline ULT being scheduled too frequently in some cases.

This issue is not relevant in master until the breadcrumb MR from @sramesh is merged.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: sds/margo#53