@quba opened this Issue on June 9th 2016 Contributor

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 commented on June 10th 2016 Owner

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

@mattab commented on July 7th 2016 Owner

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 commented on July 8th 2016 Contributor

could you create a different issue, if applicable?

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

Powered by GitHub Issue Mirror