192 reputation
18
bio website about.me/ericrrath
location
age
visits member for 2 years, 9 months
seen Dec 3 at 16:28

May
19
awarded  Notable Question
Nov
21
accepted Can MySQL use an index to calculate SUM?
Nov
21
comment Can MySQL use an index to calculate SUM?
@ypercube and @jynus -- sorry, that was a typo, should have been page.customer_id = 1234. Edited to correct, thanks for finding it.
Nov
21
revised Can MySQL use an index to calculate SUM?
Correct typo
Nov
21
answered MySQL requires FORCE INDEX on huge table and simple SELECTs
Nov
21
asked Can MySQL use an index to calculate SUM?
May
28
accepted How often should MySQL (stock, Percona, etc.) be upgraded?
May
28
awarded  Commentator
May
28
comment How often should MySQL (stock, Percona, etc.) be upgraded?
Thanks, Rolando, you've given a lot of good feedback about how to upgrade, and factors to consider. Do you have any specific guidelines for when to upgrade, or how often? Do you upgrade on a schedule, or only when necessitated by a bug fix or new feature?
May
28
comment How often should MySQL (stock, Percona, etc.) be upgraded?
Does your feedback change if the scope of the upgrade is narrowed to a dot-release (e.g. Percona Server 5.5.21 to 5.5.30)? Updating often spreads the impact of changes over a number of upgrade events, reducing the risk for each event at the expense of more planned work and potential downtime. Updating less often minimizes the planned work and potential downtime, but at a higher risk of problems from more changes at once. Where is the sweet spot? For comparison, we update much of the other software on a quarterly schedule.
May
24
comment How often should MySQL (stock, Percona, etc.) be upgraded?
Ha, I deleted my comment after I saw your Epilogue but before I saw your comment.
May
24
awarded  Informed
May
24
awarded  Editor
May
24
revised How often should MySQL (stock, Percona, etc.) be upgraded?
deleted 25 characters in body
May
24
asked How often should MySQL (stock, Percona, etc.) be upgraded?
Apr
15
awarded  Supporter
Mar
20
awarded  Popular Question
Jun
8
comment MySQL query took 98 seconds to run but EXPLAIN looks okay
I think rows_examined excludes index access. This might be far-fetched, but maybe the pages containing the indexes were not in the pool, had to be loaded from disk, and high IO led to contention and slow performance. How large is the database in question? Do you have access to sar logs, or anything else that would show CPU, IO, etc on the system at the time of the slow query? That might shed some more light on the issue.
Jun
8
comment MySQL query took 98 seconds to run but EXPLAIN looks okay
It's also possible that the original query took a long time due to other activity on the server at the time. I.e. MySQL may have been contending with another process for some shared resource like CPU or disk IO.
Jun
8
comment MySQL query took 98 seconds to run but EXPLAIN looks okay
The size of the buffer pool is controlled by the innodb_buffer_pool_size ( dev.mysql.com/doc/refman/5.5/en/… ). But I think you might want to keep it around, and if you have enough memory, adjust the size of the buffer pool to accomodate the "active set" of your data.