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

Performance, 10k Visitors and 100% CPU #2683

Closed
anonymous-matomo-user opened this issue Sep 27, 2011 · 12 comments
Closed

Performance, 10k Visitors and 100% CPU #2683

anonymous-matomo-user opened this issue Sep 27, 2011 · 12 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. worksforme The issue cannot be reproduced and things work as intended.

Comments

@anonymous-matomo-user
Copy link

Hello

My server (Windows 20088 R2;Fast-CGI;mysql) is using 100% of my CPU between 8h - 18 h. I already have installed the cronjob and increased the memory-limit to 1512MB but no change.
Can somebody help me to improve the performance ?

Note: Server has 11 cores and 8-12Gb RAM

@anonymous-matomo-user
Copy link
Author

Attachment: Server-Performance
server.gif

@anonymous-matomo-user
Copy link
Author

Attachment: Task Manager
schedule.gif

@mattab
Copy link
Member

mattab commented Sep 27, 2011

It looks like your CPU goes 100% during the archiving and is then nearly idle (tracking only).

I agree that with 11cores and so much RAM, it should behave a lot better. How many pages do you track per day?

How many rows in piwik_log_action (can you take screenshot of phpmyadmin overview of your tables with sizes + row count)?

Finally, a "quick fix" solution is to set timeout to 100000 so that you effectively disable "real time" reporting for "today" and only access yesterday and before. Today will be archived in the first archiving run of the day in your website's timezone.

@anonymous-matomo-user
Copy link
Author

How many pages do you track per day?
At the moment piwik is tracking between 60-70 websites.
How many rows in piwik_log_action (can you take screenshot of phpmyadmin overview of your tables with sizes + row count)?
The piwik_log_action table has 123486 rows and its size is 20MB.
Finally, a "quick fix" solution is to set timeout to 100000 so that you effectively disable "real time" reporting for "today" and only access yesterday and before. Today will be archived in the first archiving run of the day in your website's timezone.
Which timeout do you mean ? The archiving interval ?

@anonymous-matomo-user
Copy link
Author

Attachment: Phpmyadmin
logaction.gif

@mattab
Copy link
Member

mattab commented Sep 27, 2011

how many pages views do you track ?

The archiving interval ?
yes, in http://piwik.org/docs/setup-auto-archiving/

@anonymous-matomo-user
Copy link
Author

how many pages views do you track ?
About 10 000 visitors and between 60-70websites. The archiving interval is 3600seconds.

@anonymous-matomo-user
Copy link
Author

Attachment: Page Views
pageViews.gif

@anonymous-matomo-user
Copy link
Author

Attachment:
performance.gif

@anonymous-matomo-user
Copy link
Author

Attachment:
taskmanagerprocesses.gif

@anonymous-matomo-user
Copy link
Author

Is piwik able to handle 10 000 visitis in 12h ?

Note: Why is the ticket closed? The issue is still there ...

@mattab
Copy link
Member

mattab commented Sep 28, 2011

Piwik should handle tracking without problem, the problem is that you process "today" report and "current week" current month current year EVERY hour. This is too much. There is a new archiving script in development that will make things better but in the meantime, put archive timeout to 10000 par exemple (every 3 hours) and it will be better.

Also please enable mysql slow query log to see if there any abnormal slow query.

EDIT: see: https://piwik.org/docs/setup-auto-archiving/

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. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

2 participants