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

--concurrent-requests-per-website works differently for day and other periods #10281

Open
quba opened this issue Jul 8, 2016 · 0 comments
Open
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo.

Comments

@quba
Copy link
Contributor

quba commented Jul 8, 2016

For the day period, --concurrent-requests-per-website starts with "all visits" and then proceeds with segments. For other periods, it starts immediately with "all visits" and first X segments. It's a waste of time to start with only one thread of daily archiving. If it's a hack to be able to check if there is new raw data, I suggest moving this check BEFORE starting the real archiving process.

@quba quba changed the title --concurrent-requests-per-website --concurrent-requests-per-website works differently for day and other periods Jul 8, 2016
@mattab mattab added the c: Performance For when we could improve the performance / speed of Matomo. label Jul 15, 2016
@mattab mattab added this to the 2.16.x (LTS) milestone Jul 15, 2016
@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Aug 23, 2016
@mattab mattab modified the milestones: 2.16.x (LTS), Mid term Aug 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo.
Projects
None yet
Development

No branches or pull requests

2 participants