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

Concurrent requests are not working as one can assume #10728

Open
marucha opened this Issue Oct 12, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@marucha

marucha commented Oct 12, 2016

We have one site with 16 segments, when we will run archiving process with concurrent-requests-per-website=8 then archiving will run 8 threads.
But when 6 threads will finish job after 10 minutes we will have only 2 threads active because archiving process will wait until all threads doesn't finish job and then run another 8 threads.
It should run new thread when one will finish job, this way you have always 8 threads running at a time.

@mattab mattab added this to the Mid term milestone Nov 12, 2016

@filippog

This comment has been minimized.

Show comment
Hide comment
@filippog

filippog Dec 27, 2017

FWIW I agree it would be nice to have no idle threads. To make sure I've understood: in the case above it would mean constantly feeding the threads with archival requests to make, IOW keep working on jobs if there are idle threads?

filippog commented Dec 27, 2017

FWIW I agree it would be nice to have no idle threads. To make sure I've understood: in the case above it would mean constantly feeding the threads with archival requests to make, IOW keep working on jobs if there are idle threads?

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