Not the answer you need?
Register and ask your own question!

sizing innodb files

acristiaacristia EntrantCurrent User Role Beginner
I am looking for some tips to correctly size the innodb tablespace.

The whole database is about 10GB and I couldn't really find which es better for MySQL/innodb tablespace (assuming one tablespace and not per table tablespace):
- un big innodb file
- several smaller innodb files (eg . 5 files x 2GB)

We are using AIX 5.3 (which support large filesystems) an MySQL 5.0.24.

Thanks in advance.



  • PeterPeter Percona CEO Percona Moderator Role
    If you're not planning placing files on different partitions and if your file system supports files over 2GB in size I would go with single large file, it is generally more efficient for flushing dirty data pages.
  • acristiaacristia Entrant Current User Role Beginner
    We are not planning placing files on different partitions because we are using raid 0+1.

    So we will follow your suggestion , using a single file for the tablespace.


  • iyeatiyeat Entrant Current User Role Beginner
    What about in the case of extremely large data files? We are using MySQL with innodb attached to a RAID device configured with RAID 5. Our data is approximately 300GB but is only going to grow larger. Would you still suggest going with one large file? Or would you break the files out into smaller sizes?

    We currently have 40 4GB files configured in our setup, but are really looking for a formula that is optimal for our servers.




    Server specs: MySQL 5.0.37 Mac OS X Server 10.4.10 on an Xserve with 16GB RAM attached to a 3TB Xserve RAID via fibre.
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.