ing the secondary indexes after
>> > the
>> > data import or such alters are complete.
>> >
>> > Regards,
>> > Akshay Suryavanshi
>> >
>> >
>> > On Fri, Sep 28, 2012 at 1:56 AM, Rick James
>> > wrote:
>> >>
>> &
I try to figure out something observing the stats with SHOW STATUS. There are
some reads, writes, etc that tell something about what is going on.
Looking just at the file sizes is likely going to not tell much about the
progress.
If there is a better way to monitor this progress, I would li
Am 27.09.2012 23:15, schrieb Larry Martell:
>> Indexes are slowing this down. your calculation of 79 hours should be
>> correct, only if there are no unique indexes, otherwise this will slow down
>> more as the data increases.
>
> It is what it is - there's no free lunch - dropping the indexes, do
you carry this operation by adding the secondary indexes after
>> > the
>> > data import or such alters are complete.
>> >
>> > Regards,
>> > Akshay Suryavanshi
>> >
>> >
>> > On Fri, Sep 28, 2012 at 1:56 AM, Rick James
>&
ndo logs.
> >>
> >> > -Original Message-
> >> > From: Larry Martell [mailto:larry.mart...@gmail.com]
> >> > Sent: Thursday, September 27, 2012 1:20 PM
> >> > To: Rick James
> >> > Cc: mysql mailing list
> >> >
gt;> > To: Rick James
>> > Cc: mysql mailing list
>> > Subject: checking progress of alter table on an InnoDB table (Was: Re:
>> > checking progress of alter table on a MyISAM table)
>> >
>> > So we changed the table from MyISAM to InnoDB. I read
nal Message-
> > From: Larry Martell [mailto:larry.mart...@gmail.com]
> > Sent: Thursday, September 27, 2012 1:20 PM
> > To: Rick James
> > Cc: mysql mailing list
> > Subject: checking progress of alter table on an InnoDB table (Was: Re:
> > checking progress of a
gt; -Original Message-
>> From: Larry Martell [mailto:larry.mart...@gmail.com]
>> Sent: Thursday, September 27, 2012 1:20 PM
>> To: Rick James
>> Cc: mysql mailing list
>> Subject: checking progress of alter table on an InnoDB table (Was: Re:
>> checking progress of
: checking progress of alter table on an InnoDB table (Was: Re:
> checking progress of alter table on a MyISAM table)
>
> So we changed the table from MyISAM to InnoDB. I read that the 'undo
> log entries' shown in 'show engine innodb status' would correspond to
&g
So we changed the table from MyISAM to InnoDB. I read that the 'undo
log entries' shown in 'show engine innodb status' would correspond to
the number of rows that have been operated on throughout the process
of the ALTER. The table we're altering has 115,096,205 rows, and the
alter's been running f
2012/09/26 09:31 -0700, Rick James
You could look at the .TYD and .TYI file sizes and compare to the .MYD and
.MYI, but that can be deceptive. If the table is really big, and has lots of
indexes, the generation of the indexes might go slower and slower -- hence any
math on the sizes w
Not really.
You could look at the .TYD and .TYI file sizes and compare to the .MYD and
.MYI, but that can be deceptive. If the table is really big, and has lots of
indexes, the generation of the indexes might go slower and slower -- hence any
math on the sizes would be optimistic.
> -Origi
12 matches
Mail list logo