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 degradation after update from 2.9.2 -> 2.11.2 #7416
Comments
Do you have munin or some similar monitoring platform? I saw what appears to be a doubling in mysql temp tables (and worse, disk tables) in 2.10 - would be interested to know if others have as well. This isn't fixed even in 2.12-b3. |
+1 on nginx / CentOS 6 / php 5.3.3 |
@GreenReaper Is the table size increase in the archive tables? If so, this issue is tracked here: #7181 . Can you take a look at the last comment there and see if it helps you? |
Hi there, |
@GreenReaper Those queries use temporary tables, but I wouldn't expect them to be stored on disk, as they should not select much data. Can you see what happens when you run those queries yourself w/o the GROUP BY/MIN and ORDER BY/LIMIT? How many rows do they end up selecting? |
Let's continue discussion in #7440 |
After upgrading from 2.9.2 to 2.11.2 our server can handle only about half of the requests than before the upgrade (from ~740 req/s to ~400 req/s). Due to the database upgrades, i can't go back to 2.9.2.
The bottleneck is cpu, mostly consumed by php fcgi threads.
Server Setup:
FreeBSD 10.1, lighttpd 1.35, php 5.6.6, mysql 5.6
The text was updated successfully, but these errors were encountered: