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

Archiving should trigger limited number of concurrent requests #5035

mattab opened this issue Apr 23, 2014 · 1 comment


Copy link

@mattab mattab commented Apr 23, 2014

Currently if there are eg. 20 custom segments to generate for a given website, the auto archive command core:archive will trigger 20 concurrent requests to the API.

This can result in some of these requests failing. Instead we should only process at the same time a max count of requests, so that we don't overload the server.

This change will result in better performance of archiving and more reliability when there are many custom segments to pre-process.


This comment has been minimized.

Copy link
Member Author

@mattab mattab commented Apr 23, 2014

In 135624d: Fixes #5035 CliMulti can now trigger a limited number of concurrent requests.
This is set to three concurrent processes in core:archive command.
Refs #4903

@mattab mattab added this to the 2.2.1 - Piwik 2.2.1 milestone Jul 8, 2014
@mattab mattab added T: Task labels Jul 8, 2014
@mattab mattab self-assigned this Jul 8, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…ncurrent requests.

This is set to three concurrent processes in core:archive command.
Refs matomo-org#4903
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.