June 20, 2013

Post: Troubleshooting MySQL Memory Usage

… some events ? If you can’t get fancy graph quickly you can use this…_size per connection) are all connection buffers and so if you close connection MySQL3. row *************************** SESSION_ID: 7231 TABLE_SCHEMA: test TABLE_NAME: z ENGINE: InnoDB NAME: #sql516_1c3f_0 TABLE_ROWS: 0 AVG_ROW

Post: Modeling MySQL Capacity by Measuring Resource Consumptions

get CPU consumption per query ? You can take a look at procfs for MySQL process: root@ubuntu:/var/log/mysql# …3.53k 0.99 # Rows affecte 0 0 0 0 0 0 0 # Rows read 5.25M 0 507.86k 3Per-query information from mk-query digest (I omit queries text for client privacy) # Query 1: 0 QPS, 0x concurrency, ID

Post: Emulating global transaction ID with pt-heartbeat

3. row *************************** ts: 2011-08-03T18:12:18.001960 server_idper server. It just works. Everyone who runs replication should be running pt-heartbeat already to get

Post: MySQL Indexing Best Practices: Webinar Questions Followup

…worse then “WHERE a IN (2,3,4)”? Another word is …the index from (vendor_id) to (vendor_id,order_id) you will make it…have, which is 64 per table in recent MySQL versions. However it … on a table with 11M rows I’ve seen cardinality … scanning data in index order MySQL gets data in already sorted order …

Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

PER_THOUSAND_GETS: 4 * YOUNG_MAKE_PER_THOUSAND_GETS: 0 NOT_YOUNG_MAKE_PER_THOUSAND_GETS: 0 *NOT_YOUNG_MAKE_PER_THOUSAND_GETS3 rows in set (0.12 sec) mysql> select * from information_schema.innodb_buffer_pool_stats\G *************************** 1. row *************************** POOL_ID

Post: Identifying the load with the help of pt-query-digest and Percona Server

MySQL. This is very helpful for measurement as otherwise we might not catch some long running connections. Now let’s get…: # Time: 111229 3:11:26 # User@Host: msandbox[msandbox] @ localhost [] # Thread_id: 1 Schema: test…4ms, it sends 202 rows for which it has to examine 1012 rows (per every query), …

Post: Beware of MySQL Data Truncation

row affected, 1 warning (0.00 sec) mysql> select * from article_comment; +————+————+ | article_id | comment_id | +————+————+ | 4294967295 | 1 | | 4294967295 | 1 | | 4294967295 | 1 | +————+————+ 3 rows…to happen – you get A LOT… of comments per item. Note…

Post: The MySQL optimizer, the OS cache, and sequential versus random I/O

row *************************** Name: fact Engine: MyISAM Rows: 147045493 Avg_row_length: 117 Data_length: 17217646764 Index_length: 11993816064 mysqlid = dim2.dim2_idget evicted from memory by the cache’s LRU policy, because they are frequently used — once per row

Post: Percona XtraDB Cluster: Multi-node writing and Unexpected deadlocks

… cost of one network roundtrip per node (which is done in …PRIMARY` of table `test`.`autoinc` trx id 83B lock_mode X locks …get lock; try restarting transaction node1 mysql> select * from autoinc; +—+——-+ | i | j | +—+——-+ | 1 | node3 | | 4 | node2 | | 7 | node2 | +—+——-+ 3 rows

Post: Connecting orphaned .ibd files

…innodb_file_per_table …MySQL server. If you try to very often you’ll get an error in the log: InnoDB: Error: tablespace idmysql> select * from INNODB_SYS_INDEXES WHERE TABLE_ID = 13G *************************** 1. row *************************** TABLE_ID: 13 ID: 15 NAME: PRIMARY N_FIELDS: 1 TYPE: 3