Draft
Conversation
Owner
|
In my experiments, I used the following approach: I create a Unix socket in a temporary folder, listen to it, and create a yabai signal that sends requests there. I think the following signals would be useful: Here is an example of sending data to the socket: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request implements a new event-based provider API for any conforming space providers. The main motivation for this PR is to address the high CPU usage of Barik and its parent provider process (i.e. yabai, aerospace), which we'll refer to as PPP from now on.
Currently, Barik uses a polling/timer-based way to check for changes in the spaces or windows by querying the spaces and their windows every 0.1 seconds. While simple, this is vastly inefficient for both Barik and the PPP because of the vast amount of system resources and calculations used every time the space querying function is called.
This PR implements a new approach into monitoring for space changes--why not rely on events from the PPP instead? This way, the cost for parsing and interpreting the space changes from the PPP is minimal and, most importantly, only happens when it needs to.