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

It seems that the forked worker is only working serially #114

Open
contentfree opened this issue Jan 4, 2016 · 0 comments
Open

It seems that the forked worker is only working serially #114

contentfree opened this issue Jan 4, 2016 · 0 comments
Assignees

Comments

@contentfree
Copy link
Collaborator

This is a rather strange one. I have a queue configured to be worked by 16 threads, and looking at htop it does appear there are that many threads working. But watching the backburner logs (and the general throughput) it's only working one job at a time. So if there's a pause in the handling of one job (say a long response from an external service) then all other jobs are held back until that completes.

I reconfigured the queue to use one worker and got the same throughput. I'll keep digging into it to see if I can determine if it's my app's usage of Backburner that's doing it or if it's Backburner itself.

@contentfree contentfree self-assigned this Jan 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant