[drupal-devel] IRC Chat with MySQL Founder and MySQL developer team
Hello, as a follow up to OSCON I have arranged a chat with the MySQL development team. I met and talked with one of the founders of MySQL, David Axmark. I suggested that the Drupal community would like to learn how to better use MySQL as well as provide feedback to the developers so that they understand our requirements in the design of Drupal. I would like to put performance as one of the top points of discussion. David suggested a few topics as well: the optimizer, gui tools, PHP driver or the prepared statment support. Depending on what we want to talk about he will have the right team members attend the chat. Let's get a list of prioritized topics to discuss and then work on a mutual meeting time. Cheers, Kieran
Kieran, thanks for this idea. I think the GUI part would be less important for Drupalers than other aspects of MySQL since we mainly use it from PHP. Performance would be something to look forward to. Other points: - How much performance degradation does InnoDB introduce? We all know InnoDB is good for referential integrity, transactions, ...etc. but it does increase overhead. How much of that is expected for a CMS type application. - Is MySQL planning to do away with the serious drawback of not complaining about syntax that is not supported by the current engine? For example, if you give an option that requires InnoDB to work, but you are using MyISAM, it will silently accept it, without complaining, giving the user a false sense that the operation was successful. On 8/23/05, Kieran Lal <kieran@civicspacelabs.org> wrote:
Hello, as a follow up to OSCON I have arranged a chat with the MySQL development team. I met and talked with one of the founders of MySQL, David Axmark. I suggested that the Drupal community would like to learn how to better use MySQL as well as provide feedback to the developers so that they understand our requirements in the design of Drupal.
I would like to put performance as one of the top points of discussion. David suggested a few topics as well: the optimizer, gui tools, PHP driver or the prepared statment support. Depending on what we want to talk about he will have the right team members attend the chat.
Let's get a list of prioritized topics to discuss and then work on a mutual meeting time.
On 24 Aug 2005, at 22:55, Khalid B wrote:
- How much performance degradation does InnoDB introduce? We all know InnoDB is good for referential integrity, transactions, ...etc. but it does increase overhead. How much of that is expected for a CMS type application.
This would be my main question too. Furthermore, I wonder if someone of the MySQL team could spend some time looking at our database scheme and/or slow query log. If so, they must take into account the fact that we aim for ANSI MySQL compliance; MySQL-isms are not an option. -- Dries Buytaert :: http://www.buytaert.net/
Here is the list for discussion. 1) Overhead of innodb and need for CMS. 2) Spend some time looking at our database scheme and/or slow query log. If so, they must take into account the fact that we aim for ANSI MySQL compliance; MySQL-isms are not an option. 3) Better error handling for Innodb. 4) Replication topologies to support higher posting volumes. I'll pass the list on and find out what their teams availability is. Cheers, Kieran On Aug 24, 2005, at 11:47 PM, Dries Buytaert wrote:
On 24 Aug 2005, at 22:55, Khalid B wrote:
- How much performance degradation does InnoDB introduce? We all know InnoDB is good for referential integrity, transactions, ...etc. but it does increase overhead. How much of that is expected for a CMS type application.
This would be my main question too.
Furthermore, I wonder if someone of the MySQL team could spend some time looking at our database scheme and/or slow query log. If so, they must take into account the fact that we aim for ANSI MySQL compliance; MySQL-isms are not an option.
-- Dries Buytaert :: http://www.buytaert.net/
Kieran For points 1 and 3, I would group them together since they are related to the InnoDB storage engine, and word them something like this, so he is prepared for the questions: 1) InnoDB a) Features and advantages of InnoDB ina nutshell (transactions, referential integrity, ...etc.) b) Considerations for moving an application to InnoDB from MyISAM. The application is Drupal, and hence a CMS one, where the mix is a lot of reads relative to the writes. c) Overhead imposed by InnoDB compared to the speed of MyISAM which is one of MySQL's fortes. d) What MySQL AB intends to do with the problem of the SQL parser not returning errors when the storage engine does not support a command or a feature, giving a false sense of successful execution? This is one of the critiques here http://sql-info.de/mysql/database-definition.html#2_3 http://sql-info.de/mysql/database-definition.html#2_4
participants (4)
-
Dries Buytaert -
Khalid B -
Khalid B -
Kieran Lal