11 messages in com.mysql.lists.clusterRe: Performance
FromSent OnAttachments
Manuel Jenne29 Jun 2005 14:50 
Simon Garner29 Jun 2005 15:33 
Jonathan Miller29 Jun 2005 15:50 
Simon Garner29 Jun 2005 16:03 
Jonathan Miller29 Jun 2005 16:14 
Stewart Smith29 Jun 2005 20:09 
Mikael Ronström30 Jun 2005 00:48 
Manuel Jenne30 Jun 2005 01:12.bench, .bench
Stewart Smith30 Jun 2005 03:16 
Manuel Jenne30 Jun 2005 03:33 
Mikael Ronström30 Jun 2005 05:23 
Subject:Re: Performance
From:Mikael Ronström (mik@mysql.com)
Date:06/30/2005 12:48:45 AM
List:com.mysql.lists.cluster

Hi,

2005-06-30 kl. 01.04 skrev Simon Garner:

Hi Jonathan,

On 30/06/2005 10:50 a.m., Jonathan Miller wrote:

Simon, Maybe you would like to give me examples of "basic MySQL functionality" that you feel is missing are not up to par? We are away looking to improve. Thanks JBM

I was mostly referring to the problems with it choosing the wrong indexes for JOINs and putting JOINs in the wrong order sometimes. This has just been causing me a lot of issues today so I felt like venting ;)

We are doing lots of work on improving the integration of MySQL Cluster also in the SQL optimiser area in 5.1, there are some specific work tasks assigned to handle this problem.

Also problematic is how it deals with ALTER TABLE by dropping and recreating the table, which requires all the SQL nodes (except one) to be shut down first to avoid table corruption.

You don't need to shutdown all SQL nodes, there is a feature in the management client that temporarily shuts out all SQL nodes except one in the cluster. This also safeguards any ALTER TABLE operations.

ndb_mgm> ENTER SINGLE USER MODE <node_id> Perform ALTER TABLE operations in SQL node with given <node_id> When completed ndb_mgm>EXIT SINGLE USER MODE

We also have ideas of how to improve in this area, some simple ALTER TABLE operations will hopefully be available as on-line changes already in 5.1.

Sorely missing as well, though not really "basic" functionality, are FULLTEXT indexes and foreign key support.

FULLTEXT I noted a lot of requests for at the Users conference so it is most definitely on the radar.

Disk-based tables will also be nice!

Non-index fields will be possible to place on disk in 5.1 at least.

Thx for the venting, it is good for us to know what are the problems that hurt the most so that we can prioritise our development efforts.

Rgrds Mikael

cheers -Simon

-- MySQL Cluster Mailing List For list archives: http://lists.mysql.com/cluster To unsubscribe: http://lists.mysql.com/cluster?unsub=mik@mysql.com

Mikael Ronstrom, Senior Software Architect MySQL AB, www.mysql.com

Jumpstart your cluster: http://www.mysql.com/consulting/packaged/cluster.html