June 19, 2013

Post: MySQL Query Patterns, Optimized - Webinar questions followup

… on “MySQL Query Patterns, Optimized” for Percona MySQL Webinars.  If you missed … queries (e.g. temp tables)? For performance, it’s hard to make …primary key solution for random selection only work when the IDs for movies are… sequence after making certain insert/update/delete operations.  If you have…

Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

MySQL replication to using replication using GTIDs 1. Temporary tables – CREATE and DROP TEMPORARY tables are not supported inside transaction. 2. UpdatesSELECT – It is not supported to perform

Post: 10 years of MySQL User Conferences

for MySQL. Facebook mentions they have over 1,800 MySQL Servers. MySQL Enterprise provides Monthly Rapid Updates [MRU] while Community MySQL versions updated every quarter or so. MySQL

Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

For RPM/deb packages, this library will be available for download from our repositories. Benchmark showing the impact of memory allocators on MySQL performance… In case CREATE TABLE AS SELECT statement was running in…UPDATE[18-04-2013]: There was a RPM packaging regression introduced with the fix for

Post: More on MySQL transaction descriptors optimization

…the perfect case for read-only transaction optimization in MySQL 5.6, because all SELECT queries in the…the first two cases Percona Server performance is even slightly ahead of MySQL 5.6.10, but …=off –oltp-index-updates=0 –oltp-non-index-updates=0 run POINT_SELECT + UPDATE QPS test sysbench –num…

Post: Benchmarking Percona Server TokuDB vs InnoDB

…produce updates in-place (I will use INSERT .. ON DUPLICATE KEY UPDATE statements for that…for fast inserts, but it is suitable for range selects by `id`. However it will interesting how both InnoDB and TokuDB performs…_64/lib/mysql/libjemalloc.so [mysqld] gdb datadir=/mnt/data/mysql #for SSD innodb_…

Comment: MySQL Partitioning - can save you or kill you

… scanning the entire last two partitions, performance is not bad. (The last 2…would argue that single-row queries (SELECT, INSERT, DELETE, UPDATE) are similar in speed between…for PARTITIONing. I go into more details (and code) here: http://mysql.rjweb.org/doc.php/partitionmaint The third use case for

Post: SELECT LOCK IN SHARE MODE and FOR UPDATE

… sec) mysql> select * from tst for update; +—+ | i | +—+ | 1 | +—+ 1 row in set (0.00 sec) #Standard SELECT does not see rows while SELECT for UPDATE and LOCK… by like because locks are taken on Innodb level before MySQL performs like matching, and row is not unlocked if it does…

Post: Scaling problems still exist in MySQL 5.5 and Percona Server 5.5

performance at 1 thread to the peak performance we see the number is 2.3 for Percona Server 5.1 and around 6 forfor_mysql,ha_innobase::general_fetch,handler::read _multi_range_next,QUICK_RANGE_SELECT::get_next,rr_quick,sub_select,do_select,JOIN::exec,mysql_select,handle_select

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

perform non locking reads, meaning unless you use some modifiers such as LOCK IN SHARE MODE or FOR UPDATE, SELECTfor MySQL Performance and concurrency ? The reason is – replication. In MySQL before…SELECT would give. This by the way applies to SELECT .. LOCK IN SHARE MODE and SELECTFOR UPDATE