…the MySQL configuration. MySQL Configuration I used Percona Server 5.5.22… = 4 innodb_adaptive_flushing = 1 innodb_adaptive_flushing_method… have a better view of the whole picture. …performance to improve, but they have an impact on the write performance. Well most of the apps rely on read performance…
Post: Derived Tables and Views Performance
August 31, 2006 By 14 Comments
Starting MySQL 4.1, MySQL had support for what is called derived tables, inline views or basically subselects in the from clause. In MySQL 5.0… they compare in terms of performance ? Derived Tables in MySQL 5.0 seems to have different implementation from views, even though I would expect…
Post: Using Flexviews - part two, change data capture
March 25, 2011 By 11 Comments
… tables for changes. Improve ETL performance by identifying the data which has changed. Maintain materialized views with Flexviews (the primary purpose of… MySQL 5.1 or aren’t using RBR, then it is possible to set up a dedicated MySQL slave which has log_slave_updates=1…: MySQL 5.1+ row based logging (binlog_format=1) unique server_id in the my.cnf log_slave_updates=1, if this is a MySQL slave…
Post: Death match! EBS versus SSD price, performance, and QoS
February 21, 2011 By 54 Comments
… sda3 25.5 2.7 1.6 3.8 0.2 1.5 47% 1 78041.7 sda3 25.5 1.2 0.7 4.5 0.1 0… output of iostat.) I would characterize this as very good performance. Sub-millisecond latencies to disk, pretty much consistently, for reads… all aggregated together in each line. I can switch the view of the same data to look at it disk-by… write 1.4 MB/s, and we’re being stalled for a quarter of a second sometimes. This is causing acute performance…
Post: High-Performance Click Analysis with MySQL
December 22, 2008 By 13 Comments
…rows as you have unique ads per day. Viewed this way, suddenly you start to hate the …save that work by either using MySQL 5.1‘s row-based replication, or in MySQL 5.0 and earlier, doing the work… star schemas. The problem is that MySQL doesn’t tend to perform well on a data warehousing workload.Â…
Post: MySQL Northern European Customer Conference
October 17, 2007 By 7 Comments
…MySQL 5.1 (Q1 2008) and MySQL 6.0 (Q4 2008) – which sounds pretty ambitious to me but we shall see how many resources 5.1… in 6.x series proper performance monitoring instrumentation and semi-synchronous…MySQL 6.0 which are pretty cool and which we still do not have a time to take a closer view…
Post: Which Linux distribution for a MySQL database server? A specific point of view.
December 8, 2011 By 37 Comments
… may carry new features or slight performance improvements, however these days it is rarely important to MySQL users. If it is to… MYSQL, upgrade MySQL, 10x start/stop MySQL, upgrade MySQL, downgrade MySQL, upgrade MySQL, install a security fix for something, 20x start/stop MySQL, upgrade MySQL, … . Restarting and changing MySQL…. In this particular case the problems were with MySQL packages upgraded from 5.1 to 5.5. The former were not fully uninstalled, the latter…
Post: MySQL on Amazon RDS part 1: insert performance
March 15, 2011 By 37 Comments
…) is a cloud-hosted MySQL solution. I’ve had some clients hitting performance limitations on standard EC2 servers…minute (click on the image for a bigger view): We can deduce a few things from this….more statistics and finer-grained samples, say, every 5 seconds instead of every minute, and some …
Post: A workaround for the performance problems of TEMPTABLE views
May 19, 2010 By 7 Comments
…5 | const | 130 | 100.00 | Using where; Using index | +—-+————-+——-+——+—————+——+———+——-+——+———-+————————–+ 1 row in set, 1 warning (0.00 sec) Notice the rewritten SQL query: mysql… query complexity for improved view performance…
Post: MySQL VIEW as performance troublemaker
August 12, 2007 By 53 Comments
…MySQL 5.0 will fail and perform very inefficiently in many counts. MySQL has two ways of handling the VIEWS – query merge, in which case VIEW…Extra: Using where; Using join cache *************************** 2. row *************************** id: 1 select_type: PRIMARY table: type: ALL possible_keys: …
