meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 3 months |
| seen | Apr 19 at 20:05 | |
| stats | profile views | 3 |
|
Feb 26 |
comment |
Update to session table slow @automatem Glad this worked for you. Came across this as well that might be worth looking at: stackoverflow.com/questions/2897765/… |
|
Feb 25 |
comment |
Update to session table slow @automatem So this sped up your queries so they no longer show in slow query log? Memory storage engine is definitely for session management. My reason for not mentioning it: having enough innodb_buffer_pool for the whole database, everything winds up acting like a memory storage engine over time (in theory anyway) but with added benefits. Glad it was useful for you. |
|
Feb 22 |
revised |
Update to session table slow added 18 characters in body |
|
Feb 22 |
revised |
Update to session table slow added 128 characters in body |
|
Feb 22 |
revised |
Update to session table slow added 128 characters in body |
|
Feb 22 |
revised |
Update to session table slow added 369 characters in body |
|
Feb 22 |
revised |
Update to session table slow deleted 162 characters in body |
|
Feb 22 |
revised |
Update to session table slow speeding up updates |
|
Feb 22 |
revised |
Update to session table slow add support for query_cache recommendation |
|
Feb 21 |
revised |
Update to session table slow added 162 characters in body |
|
Feb 21 |
awarded | Editor |
|
Feb 21 |
revised |
Update to session table slow added 167 characters in body |
|
Feb 21 |
answered | Update to session table slow |
|
Feb 21 |
comment |
Mysql optimization help note: read through dbasquare.com/2012/04/04/how-to-resize-innodb-logs before changing the innodb_log_file_size |
|
Feb 21 |
comment |
Mysql optimization help innodb_log_file_size={the value should be innodb_buffer_pool_size/2 } |
|
Feb 21 |
comment |
Mysql optimization help thread_cache_size = {at least 60 and near the number of connections established in about 2 seconds} |
|
Feb 21 |
awarded | Analytical |
|
Feb 21 |
awarded | Informed |
|
Feb 20 |
awarded | Teacher |
|
Feb 20 |
comment |
Mysql optimization help That's only for Solaris systems, so no need to fiddle with that. (see dev.mysql.com/doc/refman/5.1/en/…) The next step after these settings in my.cnf is tracking down the cause of the spikes. When you connect to mysql (see section Connecting to the MySQL Server For the First Time: dev.mysql.com/tech-resources/articles/…) if you issue the command show full processlist; (as dba.stackexchange.com/users/11651/michael-sqlbot mentioned) you can gather evidence of the root cause of high IO. |
