Hi Johan,
Thanks for your reply. Theorically the fragmented tables not offer the best
performance to the InnoDB engine, that's correct or not?
I don't know if is a problem or not, is a doubt/question for me. I'm not
sure if is an atypical behaviour.
Thanks in advance.
Regards,
Antonio.
*please* don't use reply-all on mailing-lists
the list by definition distributes your message
Am 30.06.2014 13:14, schrieb Antonio Fernández Pérez:
Thanks for your reply. Theorically the fragmented tables not offer the best
performance to the InnoDB engine,
that's correct or not?
practically
Hi Andre,
Thanks for your reply. I have checked the link and my configuration.
Innodb_file_per_table is enabled and in data directory appears a set of
files by each table.
Any ideas?
Thanks in advance.
Regards,
Antonio.
Am 27.06.2014 09:48, schrieb Antonio Fernández Pérez:
Thanks for your reply. I have checked the link and my configuration.
Innodb_file_per_table is enabled and in data directory appears a set of
files by each table.
Any ideas?
ideas for what?
* which files don't get shrinked (ls -lha)
*
Hi Reindl,
Thanks for your attention.
Following the previous mail, I have checked my MySQL's configuration and
innodb_file_per_table is enabled so, I think that this parameter not
affects directly to fragmented tables in InnoDB (In this case).
I would like to know, if is possible, why after
Hello Antonio,
On 6/27/2014 9:31 AM, Antonio Fernández Pérez wrote:
Hi Reindl,
Thanks for your attention.
Following the previous mail, I have checked my MySQL's configuration and
innodb_file_per_table is enabled so, I think that this parameter not
affects directly to fragmented tables in
- Original Message -
From: Antonio Fernández Pérez antoniofernan...@fabergames.com
Subject: Re: Optimizing InnoDB tables
I would like to know, if is possible, why after execute an analyze table
command on some fragmented table, after that, appears fragmented again.
Simple question
Hi again,
I have enabled innodb_file_per_table (Its value is on).
I don't have clear what I should to do ...
Thanks in advance.
Regards,
Antonio.
- Original Message -
From: Antonio Fernández Pérez antoniofernan...@fabergames.com
Subject: Re: Optimizing InnoDB tables
I have enabled innodb_file_per_table (Its value is on).
I don't have clear what I should to do ...
Then all new tables will be created in their own tablespace now
Have a look at this:
https://rtcamp.com/tutorials/mysql/enable-innodb-file-per-table/
--
Andre Matos
andrema...@mineirinho.org
On Jun 25, 2014, at 2:22 AM, Antonio Fernández Pérez
antoniofernan...@fabergames.com wrote:
Hi again,
I have enabled innodb_file_per_table (Its value is on).
I
Hi list,
I was trying to optimize the InnoDB tables. I have executed the next query
to detect what are the fragmented tables.
SELECT TABLE_SCHEMA,TABLE_NAME
FROM TABLES WHERE TABLE_SCHEMA NOT IN (information_schema,mysql) AND
Data_free 0
After that, I have seen that there are 49 fragmented
Hi Antonio, como esta?
What's the mysql version you're running? Have you tried to ALTER TABLE x
ENGINE=InnoDB?
-- WB, MySQL Oracle ACE
Em 24/06/2014, às 08:03, Antonio Fernández Pérez
antoniofernan...@fabergroup.es escreveu:
Hi list,
I was trying to optimize the InnoDB tables. I have
Hi Wagner,
I'm running
MySQL Percona Server 5.5.30 64Bits. No, I don't have tried to execute
ALTER TABLE (Analyze with InnoDB tables do that, or not?).
Thanks in advance.
Regards,
Antonio.
Hello Antonio,
On 6/24/2014 7:03 AM, Antonio Fernández Pérez wrote:
Hi list,
I was trying to optimize the InnoDB tables. I have executed the next query
to detect what are the fragmented tables.
SELECT TABLE_SCHEMA,TABLE_NAME
FROM TABLES WHERE TABLE_SCHEMA NOT IN (information_schema,mysql)
Am 24.06.2014 21:07, schrieb shawn l.green:
It makes a huge difference if the tables you are trying to optimize have
their own tablespace files or if they live
inside the common tablespace.
http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_file_per_table
which
Hello Reindl,
On 6/24/2014 3:29 PM, Reindl Harald wrote:
Am 24.06.2014 21:07, schrieb shawn l.green:
It makes a huge difference if the tables you are trying to optimize have their
own tablespace files or if they live
inside the common tablespace.
I have a question about:
If you want to regain some of the space used by the INNODB file you
will have to convert all INNODB tables to MYISAM (or dump them to
a SQL file), recreate the INNODB file (s) and then recreate the
original INNODB tables.
So, just to be clear, is this the right
Hi,
According to the manual -
http://dev.mysql.com/doc/mysql/en/OPTIMIZE_TABLE.html
http://dev.mysql.com/doc/mysql/en/InnoDB_File_Defragmenting.html
running a null ALTER statement - ALTER TABLE tbl-name type=INNODB; will
rebuild the table thus optimizing the way the table is written to the
The documentation is not clear on this point. Here is a quote:
'For BDB tables, OPTIMIZE TABLE is currently mapped to ANALYZE TABLE. It was
also the case for InnoDB tables before MySQL 4.1.3; starting from this
version it is mapped to ALTER TABLE.'
What is meant by its being mapped to ALTER
If I have an InnoDB table, how can I optimize it (like OPTIMIZE
TABLE for MyISAM tables)? I've seen previous posts from Heikki
saying to use ALTER TABLE, as that effectively dumps and reimports
the table, but is that true with the new 3.23.50 version that
actually has a working ALTER TABLE?
I
20 matches
Mail list logo
