June 19, 2013

Comment: INSERT INTO ... SELECT Performance with Innodb tables.

Wrong, it’s still the same in 5.5. Here is the related output from show engine innodb status: —TRANSACTION BB0E42A, ACTIVE 3 sec fetching rows, thread declared inside InnoDB 334 mysql tables

Post: Measuring the amount of writes in InnoDB redo logs

InnoDB log file size is key to InnoDB write performance. This…SHOW ENGINE INNODB STATUS OUTPUT or the Innodb_os_log_written global status variable (if you are a Percona Server user, the LSN is… me I was wrong in my redo log size calculations. After … that inserts one row at a time in a table, as fast …

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

… the table above you can with default buffer size of 256K, MariaDB 5.5 shows that Handler…rows than MySQL 5.5, as can be seen by the numbers reported for the status counter Innodb_rows_read. While MySQL 5.6 is… the optimizer made a wrong choice. It looks like that there is still improvement and …

Post: Heikki Tuuri answers to Innodb questions, Part II

Innodb besides scalability changes in later 5.0 series compact row…, crashes, or wrong query …Mysql is the main one with “innodb_buffer_pool_size=20480M”) while the bulk of the rest (9 GB) isshowed up in “show innodb status”. select * from table where id=5 show innodb status: Hash table size

Post: Heikki Tuuri Innodb answers - Part I

is one of little known new features in MySQL 5.1 Q15: How frequently does Innodb fuzzy checkpointing is activated HT: InnoDBsize of the row is less than 8100 bytes InnoDB will not allocate additional space for blobs, even if each blob is

Post: Percona Server on the Raspberry Pi: Your own MySQL Database Server for Under $80

wrongInnoDB | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, and foreign keys | YES | YES | YES | [...] mysql> SELECT “Hello World!” AS “Success!” \G *************************** 1. row

Post: Why MySQL could be slow with large tables ?

is often forgotten about is – depending if workload is cached or not different selectivity might show benefit from using indexes. In fact even MySQL…clustered keys in Innodb which combine index…The problem is not the data size – …table scans (as 60mil of rows need to be read) – this is way wrong

Comment: How to find wrong indexing with glance view

… all stored in users table(may be except looking_…show people with fotos only” and mysql can use index to filter records before fetching any rows…should benchmark and check EXPLAINS which one is better for all combinations of (…size of data (for innodb). May be I’m wrong here, but I do think that size

Post: Is disk Everything for MySQL Performance ?

… on MySQL UC2008 …when storage sizeis doing all search heavy lifting we only need to insert new data and fetch few rows to showwrong, I just it is not always the case. Another mistake isTABLE command. Let me also comment on the memory fit diagram – understanding your working set is… keep Innodb data …