May 26, 2012

Post: Joining many tables in MySQL - optimizer_search_depth

in MySQL 5.5 which can produce very expensive plan selections ? Investigating this further I found the following explanation from Timour Katchaounov in MySQL mailing list archives I have some recollection that there were few main reasons for the decision to keep exhaustive search

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

I have been working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in… new optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take…

Post: Community events around Percona Live MySQL Conference and Expo 2012

… you surely should not miss: Pythian is stepping in to organize traditional MySQL Community Dinner event during Tutorial Day of the conference… Search Day hosted by Sphinx Technologies (April 13) All these events are free to attend (registration needed) whenever you’re attending MySQL… the Feather sessions on Percona Live MySQL Conference and Expo, taking place Tuesday and Wednesday in the evening are free for anyone…

Comment: Joining many tables in MySQL - optimizer_search_depth

… a reasonable limit for the search depth (and the total number of tables) that can be optimized in reasonable time. I reached… change to plan pruning in MySQL 5.6. Ideally, the server should analyze the query and should determine the search depth based on some syntactic properties and knowledge of indexes. The problem is that it is very hard to predict in

Comment: InnoDB's gap locks

… write queries, in spite of your chosen transaction isolation level” I have two sessions with REPEATABLE READ transaction isolation level. mysql> show…) DEFAULT NULL, KEY `i` (`i`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 mysql> select * from t; +——+——–+ | i | c | +——+——–+ | 1 | miguel | | 3 | andy | | 5… | | 8 | repls | +——+——-+ Now go back to session1 and try to search the row with the value “andy”: session1> select * from t…

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

… X7542 CPUs giving 24 real cores. The workload was completely in memory in this test. I have compared Percona Server 5.1…_cur_search_to_nth_level,btr_p cur_open_with_no_init_func,row_sel_get_clust_rec_for_mysql,row_search_for_mysql…_cur_search_to_nth_level,btr_p cur_open_with_no_init_func,row_sel_get_clust_rec_for_mysql,row_search_for_mysql

Post: MySQL Full Text Search in Action

… you would desire. In general I think both of this sites have the same mistake (or shortcut) in MySQL Full Text Search configuration – relaying on minimum keyword length while their application has use cases when search for short keywords…

Post: Sphinx 2.0.2 Beta is released, Sphinx Users Conference in December

… 6 months. In fact Sphinx 2.0.3-rc is promised within 1 month. What MySQL Users will find interesting in this release… somewhere in US or Western Europe. I hope we’ll see something like it in 2012. Another thought – with Innodb Full Text Search coming up in MySQL 5.6 and Claimed to…

Post: An update on Percona Live MySQL Conference & Expo 2012

… a cadre of the core MySQL developers to submit talks about what is new in MySQL, the MySQL roadmap for the future, … DRBD, partitioning, community toolkits, security, using MySQL with NoSQL, geospatial functionality, cloud computing, Cluster, search, sharding, memcached, high availability, DevOps, …

Post: Sphinx: Going Beyond full text search

searching for “dev.mysql.com/download”" will only match dev.mysql.com domain and files within /download/ directory. Initially we implemented it in MySQL using partitioning by domain which link was pointing to. So “mysql.com” links were stored in one table group…