Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fork a hook process, instead of forking every time. #41

Open
sargon opened this issue Oct 3, 2018 · 1 comment
Open

Fork a hook process, instead of forking every time. #41

sargon opened this issue Oct 3, 2018 · 1 comment
Milestone

Comments

@sargon
Copy link
Owner

sargon commented Oct 3, 2018

We could fork a process early and then pass events by a unnamed socket.
This would solve the issue with multiple hook script instances, forking
on every event and prevent and resources over consumption by an event
spike.

@sargon sargon added this to the r3 milestone Oct 3, 2018
@sargon sargon changed the title Fork an hook process, instead of forking every time. Fork a hook process, instead of forking every time. Oct 5, 2018
Repository owner deleted a comment from rubo77 Oct 5, 2018
@sargon sargon modified the milestones: r3, r4 Mar 7, 2019
@christf
Copy link
Contributor

christf commented Sep 8, 2019

another way would be starting one process like run-parts that runs all the hooks.

EDIT: actually the run-parts approach does not solve the issue entirely. hooks for different events are still processed in parallel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants