[wp-hackers] Options table' varchar 64.

[Haluk Karamete]

THank you Morgan.

So, assuming if it's a 100 site, multi-site network where each site has as
many options as you described, this one time pain of schema change will
come at the expense of a 2.87*100 sec?

Is this understanding correct in a nut-shell?




On Tue, Jun 24, 2014 at 11:01 AM, Morgan Tocker <morgan.tocker at oracle.com>
wrote:

> Hi!
>
> On Jun 24, 2014, at 6:42 AM, Haluk Karamete <halukkaramete at gmail.com>
> wrote:
>
> > Is there a harm to change the options table so that the field names for
> the
> > transients  can have varchar 128 as opposed to varchar 64  and  if that's
> > okay, what's the best way to do this?
>
> It will lock up the table to extend the VARCHAR, while in the background
> it fills a temporary table to replace the existing table.
>
> I loaded the wp_options table with 104994 dummy records to test how long
> this would take.  On my local machine:
>
>  * 1.71 sec using InnoDB
> * ~2.84 sec when using MyISAM.
>
> Gist available for anyone wanting to try and reproduce:
> https://gist.github.com/morgo/4f23b48fd3df09fb47f6
>
> In MySQL 5.7 this will be online for InnoDB tables:
> http://dev.mysql.com/worklog/task/?id=6554
>
> - Morgan
>
> --
> Morgan Tocker
> MySQL Community Manager
> Oracle Canada - Hardware and Software, Engineered to Work Together.
> Office: Toronto, Canada
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>