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

Segement Editor is a mysql killer #4211

Closed
DaSchTour opened this issue Oct 11, 2013 · 5 comments
Closed

Segement Editor is a mysql killer #4211

DaSchTour opened this issue Oct 11, 2013 · 5 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. worksforme The issue cannot be reproduced and things work as intended.

Comments

@DaSchTour
Copy link
Contributor

I have a page with around 2000 visitors per day. When trying to use the segement editor to see some more specific data I randomly crash the server. Mysql runs on full CPU. There is a query that prepares for minutes and doesn't come to an end and apache processes take all RAM while waiting for the process to end preparing (which it never does). So this function is great for killing you server completely.
Keywords: mysql, segment editor

@mattab
Copy link
Member

mattab commented Oct 11, 2013

Select "segmented report are pre-processed" in the top option.

Setup: http://piwik.org/setup-auto-archiving/

Use Piwik 2.0 alpha from http://builds.piwik.org/

it should work

@DaSchTour
Copy link
Contributor Author

So you suggest using a Alpha Software for a productive System with over 2000 visitors per day? I hope this is a joke.
BTW: Auto archiving is activated, but that doesn't prevent segmented reports from crashing the server. What if somebody creates a new segment, auto-archive didn't run and he tries to select this segment?
This all doesn't prevent crashing the server.

@mattab
Copy link
Member

mattab commented Oct 12, 2013

Not a joke, it works quite well. I suggested because you had some urgent problem, so it definitely will not be worst (but keep a mysql backup to be safe)

@DaSchTour
Copy link
Contributor Author

well, my fast solution was du deactivate the segment editor. It looks like the fact, that the segment editor is a feature for killing the server is already obvious. So I'll have to wait for the 2.0 stable release and test again and check if the segment editor is no more a plugin in alpha state.

@gaumondp
Copy link

I think it's a bit unfair to say the Segment Editor is an alpha plugin. I have a site with about 30 000 pageviews a day and use a segment filtering 6 different IP without problem.

I'm lucky, Apache-PHP-Piwik is on a dedicated server and MySQL is on another, solely for Piwik work.

I'm not saying that it's perfect thought. There's always room for improvement.

Dali

This issue was closed.
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. Critical Indicates the severity of an issue is very critical and the issue has a very high priority. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

3 participants