Comments on: Development plans http://www.mysqlperformanceblog.com/2008/09/08/development-plans/ Everything about MySQL Performance Sat, 21 Nov 2009 05:23:57 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Vadim http://www.mysqlperformanceblog.com/2008/09/08/development-plans/comment-page-1/#comment-354741 Vadim Sat, 13 Sep 2008 01:06:01 +0000 http://www.mysqlperformanceblog.com/?p=491#comment-354741 Nils, That would be interesting to test. Before including in release we need to check if there is no stability and performance problems. About process - yeah, I have such idea, will try to write :) Nils,

That would be interesting to test.
Before including in release we need to check if there is no stability and performance problems.

About process – yeah, I have such idea, will try to write :)

]]> By: Nils http://www.mysqlperformanceblog.com/2008/09/08/development-plans/comment-page-1/#comment-354737 Nils Sat, 13 Sep 2008 00:52:04 +0000 http://www.mysqlperformanceblog.com/?p=491#comment-354737 I'm currently trying out the new Ebay Heap Engine, I've managed to get the patch to work with 5.0.68, few rejects which I think I fixed. I'm by far no expert, so next step would be to check the changes between the original patched version and the new version to see what exactly caused the rejects, doesn't seem to be a big deal though. Maybe you can write something about the actual process of creating a customized MySQL (is there something like that already out?) while you're at it ;) I’m currently trying out the new Ebay Heap Engine, I’ve managed to get the patch to work with 5.0.68, few rejects which I think I fixed. I’m by far no expert, so next step would be to check the changes between the original patched version and the new version to see what exactly caused the rejects, doesn’t seem to be a big deal though.

Maybe you can write something about the actual process of creating a customized MySQL (is there something like that already out?) while you’re at it ;)

]]> By: Vadim http://www.mysqlperformanceblog.com/2008/09/08/development-plans/comment-page-1/#comment-353513 Vadim Tue, 09 Sep 2008 01:28:41 +0000 http://www.mysqlperformanceblog.com/?p=491#comment-353513 Adam, We played with progress in processlist, but often it shows misleading information, so we decided to not include it yet. Adam,

We played with progress in processlist, but often it shows misleading information, so we decided to not include it yet.

]]> By: Adam http://www.mysqlperformanceblog.com/2008/09/08/development-plans/comment-page-1/#comment-353503 Adam Tue, 09 Sep 2008 00:47:39 +0000 http://www.mysqlperformanceblog.com/?p=491#comment-353503 Personally I think this is awesome addition, and could be integrated into your set of patches as well: http://jcole.us/blog/archives/2007/02/08/progress-in-mysql-process-list/ Personally I think this is awesome addition, and could be integrated into your set of patches as well:

http://jcole.us/blog/archives/2007/02/08/progress-in-mysql-process-list/

]]> By: Kevin Burton http://www.mysqlperformanceblog.com/2008/09/08/development-plans/comment-page-1/#comment-353499 Kevin Burton Tue, 09 Sep 2008 00:17:23 +0000 http://www.mysqlperformanceblog.com/?p=491#comment-353499 Actually we're really needing the ability to move InnoDB tables too... We wrote our own partitioning code in our distributed DB land... it supports shards and partitions (on partition per day). The problem is when we need to bring up a new DB server in a shard. We need to copy all the previous partitions. They're immutable so we should be able to copy them from a currently running version of InnoDB to another box. It might be possible to do this for a DB server which was an original clone for the current server but I need to test it. I'm not sure what happens when InnoDB has been running for a while. We actually migrated BACK to MyISAM (ug) because of this feature. (that and we saved 2x on disk space) Kevin Actually we’re really needing the ability to move InnoDB tables too…

We wrote our own partitioning code in our distributed DB land… it supports shards and partitions (on partition per day).

The problem is when we need to bring up a new DB server in a shard. We need to copy all the previous partitions.

They’re immutable so we should be able to copy them from a currently running version of InnoDB to another box.

It might be possible to do this for a DB server which was an original clone for the current server but I need to test it. I’m not sure what happens when InnoDB has been running for a while.

We actually migrated BACK to MyISAM (ug) because of this feature. (that and we saved 2x on disk space)

Kevin

]]>