Navigation Menu

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

Load Pages Row Evolution out of memory after upgrade to 3.10.0 #14667

Closed
xpader opened this issue Jul 18, 2019 · 4 comments
Closed

Load Pages Row Evolution out of memory after upgrade to 3.10.0 #14667

xpader opened this issue Jul 18, 2019 · 4 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@xpader
Copy link

xpader commented Jul 18, 2019

After upgrade to 3.10.0，I have two problem:

  1. Open Pages Row Evolution out of memory.

Response:
Matomo encountered an error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 147456 bytes) (which lead to: Allowed memory size of 268435456 bytes exhausted (tried to allocate 147456 bytes))

My php.ini set memory limit to 512M, and my website's uv and pv just about 8000 and 100000 for daily.

  1. Open Events Row Evolution show Error:

Error: The parameter 'secondaryDimension' isn't set in the Request, and a default value wasn't provided.
@tsteur
Copy link
Member

tsteur commented Jul 18, 2019

Error: The parameter 'secondaryDimension' isn't set in the Request, and a default value wasn't provided.

I've fixed this issue 5 minutes ago in #14666

The other issue I recommend increasing your memory and / or to ensure you have browser archiving disabled see https://matomo.org/docs/setup-auto-archiving/
BTW: The size of the memory would not really depend on the amount of traffic you have with row evolution since it's only handling aggregated data. The traffic would only matter if you have eg browser archiving enabled.

@tsteur tsteur closed this as completed Jul 18, 2019
@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label Jul 18, 2019
@xpader
Copy link
Author

xpader commented Jul 18, 2019

My browser archive is closed, and archive was set in crontab.

@tsteur
Copy link
Member

tsteur commented Jul 18, 2019

Thanks for letting us know. The 512MB memory might help. As said, the memory usage doesn't depend on the traffic size here unfortunately.

@xpader
Copy link
Author

xpader commented Jul 19, 2019

Yes, But the memory used was too big, I think there is room for improvement here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @xpader