Skip to content

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

Closed
Open
Opened Nov 12, 2015 by Philip Carns@carns
  • Report abuse
  • New issue
Report abuse New issue

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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: sds/archive/abt-snoozer#3