Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A abt-snoozer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sds
  • Archive
  • abt-snoozer
  • Issues
  • #3

Closed
Open
Created Nov 12, 2015 by Philip Carns@carnsOwner

more efficient method to detect stop events in scheduler

Right now the scheduler has to wake up periodically (currently every 10th of a second) to call the has_to_stop() function to see if it should shut down. This condition can be set without any change to the pool, which means it bypasses the libev signalling mechanism.

There are a few minor problems with this approach:

  • wakes up the thread more frequently than is strictly needed
  • makes xstream_join() functions take longer to complete than necessary
  • waking the scheduler up periodically may obfuscate bugs that would otherwise manifest as a scheduler hang
Assignee
Assign to
Time tracking