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

Jump to bottom

Custom date range shouldn't trigger archiving for today's day #10225

Open
quba opened this issue Jun 9, 2016 · 3 comments
Open

Custom date range shouldn't trigger archiving for today's day #10225

quba opened this issue Jun 9, 2016 · 3 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo.
Milestone
Backlog (Help wan...

Comments

@quba
Copy link
Contributor

quba commented Jun 9, 2016 •
edited

I'll explain it with an example (all websites dashboard, 100 sites, period range):

  • last30 - takes about 60-70 seconds to load, then it's quite fast when I try a few times, but after reaching daily archives' TTL, it's again very slow
  • previous30 - the first load takes a few seconds (merging archives), next loads are instant

So, I assume that last30 and any date range including today is re-archiving the current day (if there are no valid archives for that day - TTL exceeded).

This comment from the settings seems to confirm my assumption:

This affects only reports for today (or any other Date Range including today)

It would be nice to not rearchive day period if browser archiving is disabled and date range including today is requested. Additionally, a standard archiving process could remove all range archives that include today - this would let Piwik update date range archives including today after each successful cron archiving.
@tsteur
Copy link
Member

tsteur commented Jun 10, 2016

Sounds like a bug to me, especially when "browser archiving is disabled".

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Jun 10, 2016
@mattab
Copy link
Member

mattab commented Jul 7, 2016

So, I assume that last30 and any date range including today is re-archiving the current day (if there are no valid archives for that day - TTL exceeded).

Confirmed.

It would be nice to not rearchive day period if browser archiving is disabled and date range including today is requested.

I haven't confirmed, but if "today day" is re-archived in the browser even when browser archiving is disabled, then it is a bug. +1 to disable archiving of "today" in the browser when browser archiving is disabled.

Additionally, a standard archiving process could remove all range archives that include today - this would let Piwik update date range archives including today after each successful cron archiving.

could you create a different issue, if applicable?

@quba
Copy link
Contributor Author

quba commented Jul 8, 2016

could you create a different issue, if applicable?

Will do, but it makes no sense to introduce this one before fixing the bug.

@mattab mattab modified the milestones: 2.16.2, 2.16.x (LTS) Jul 14, 2016
@mattab mattab added c: Performance For when we could improve the performance / speed of Matomo. c: Accessibility When something is not usable for a certain group (eg missing contrast) or devices (eg smartphones). labels Jul 18, 2016
@mattab mattab mentioned this issue Aug 23, 2016
Closed
@mattab mattab modified the milestones: 2.16.x (LTS), Mid term Aug 25, 2016
@mattab mattab removed the c: Accessibility When something is not usable for a certain group (eg missing contrast) or devices (eg smartphones). label Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
3 participants
@tsteur @mattab @quba