thinkbot
- Total activity 275
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 67
Comments
Recent activity by thinkbot-
track slow queries in your mysql my.cnf slow_query_log=1 slow_query_log_file=mysql-slow.log long_query_time=0.1 let it run for some time then review them cd /root/ wget
-
Hey, Your settings are way too high [--] Total buffers: 1.8G global + 12.3M per thread (1000 max threads) [!!] Allocating > 2GB RAM on 32-bit systems can cause system instability [!!] Maximum poss...
-
can you run mysqltuner.pl ?
-
[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock myisam_use_mmap=1 group_concat_max_len=10000000 key_buffer_size = 4G thread_cache_size = 50 query_cache_size = 100M query_cache_li...
-
yes, I mean table cache 2048 but did y ou check what type of queries are those "non-index" can you set long query time to 0 and then run cd /root wget
-
key_buffer_size set over 110M also increase innodb_buffer_pool_size=560M InnoDB can use more and decreate table cache to 2 In your case I would turn on query cache Maybe it's time to optimize tha...
-
Becouse you got too small buffers to fit InnoDB data/indexes to RAM [!!] InnoDB data size / buffer pool: 12.8G/1.0G and you are using 32-bit system [!!] Allocating > 2GB RAM on 32-bit systems can ...
-
Yes, but in this case you should convert to InnoDB only the table which had problems with locking And previously you might not had properly configured myisam key buffer size, so that might be the p...
-
The thing is, for fast query execution it's important to have indexes (MyISAM) and data+indexes (Innodb) in memory, RAM MyISAM places only indexes in RAM, InnoDB both, indexes and data so if you ...
-
You got 15GB in MyISAM and 12GB in InnoDB For MyISAM, key_buffer_size must be higher than 620M if you use all contents indexes, so [OK] Key buffer size / total MyISAM indexes: 256.0M/620.0M set k...