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

Row Evolution can use too much memory #8169

Closed
mattab opened this issue Jun 22, 2015 · 5 comments
Closed

Row Evolution can use too much memory #8169

mattab opened this issue Jun 22, 2015 · 5 comments
Labels
c: Performance For when we could improve the performance / speed of Matomo. worksforme The issue cannot be reproduced and things work as intended.

Comments

@mattab
Copy link
Member

mattab commented Jun 22, 2015

  • Example URL to reproduce (requires login to demo)
    • Got: <b>Fatal error</b>: Allowed memory size of 536870912 bytes exhausted (tried to allocate 88 bytes) in <b>/home/piwik-demo/www/demo.piwik.org/core/Metrics.php</b> on line <b>196</b><br /> (I since reverted memory limit to 256M)
    • Expected: report loads fast and does not use more than 256M of memory
@mattab mattab added Bug For errors / faults / flaws / inconsistencies etc. c: Performance For when we could improve the performance / speed of Matomo. labels Jun 22, 2015
@tsteur
Copy link
Member

tsteur commented Jun 23, 2015

Expected: report loads fast and does not use more than 256M of memory

That's a bit a random requirement. How much does it actually take? Can you increase to 1GB and see if it works and how much it actually uses?

I think it'd be better to check if we can find a memory leak or something but a 512MB memory usage might be valid

@mattab
Copy link
Member Author

mattab commented Jun 23, 2015

After changing memory limit to 1024M, the row evolution loads. It took 1 min to load the report (period month) which is quite slow.

Surprisingly

  • it is only very slow for Period = Week or Month or Year
  • It is very fast for period = day and period = range (takes 1 second)

@mattab
Copy link
Member Author

mattab commented Jun 23, 2015

This only affects the "User cities" report, other Row Evolution reports load very fast

@mattab mattab added this to the Mid term milestone Jul 15, 2015
@mattab mattab removed the Bug For errors / faults / flaws / inconsistencies etc. label Jul 15, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
@xpader
Copy link

xpader commented Jul 15, 2019

It's also very slow in Pages report.

@mattab
Copy link
Member Author

mattab commented Oct 18, 2019

Row Evolution should be quite fast in general as long as reports are pre-processed by the cron, and that browser archiving is disabled. Will close the issue as we haven't had this issue recently.

@mattab mattab closed this as completed Oct 18, 2019
@mattab mattab added the worksforme The issue cannot be reproduced and things work as intended. label Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Performance For when we could improve the performance / speed of Matomo. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

3 participants