# innodb\_file\_per\_table for single tenant SaaS

**URL:** <https://forums.percona.com/t/innodb-file-per-table-for-single-tenant-saas/3735>\
**Category:** Other MySQL® Questions\
**Created:** [September 11, 2014, 7:06am UTC](https://forums.percona.com/t/innodb-file-per-table-for-single-tenant-saas/3735 "2014-09-11T07:06:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mysqlsaas](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mysqlsaas/32/1036_2.png) [@mysqlsaas](https://forums.percona.com/u/mysqlsaas)\
**Post date:** [September 11, 2014, 7:06am UTC](https://forums.percona.com/t/innodb-file-per-table-for-single-tenant-saas/3735/1 "2014-09-11T07:06:34Z")

</div>

We have a mySQL backed SaaS application where each customer has their own mySQL database. So think of it like a wordpress/magento etc. database for each client.

Each database has ~200 table, and we expect to have about 1,000 databases per server, so 200,000+ tables. We currently have innodb\_file\_per\_table enabled.

Our question is regarding whether we should use innodb\_file\_per\_table or not. We’ve seen some conflicting information on this:  
[LIST]  
[_]Performance: With the large number of tables, is it better or worse to use innodb\_file\_per\_table. We understand there can be issues with the number of file pointers required to have hundreds of thousands of tables open.  
[_]Stability: There is some discussion that using innodb\_file\_per\_table is safer or improves crash recorvery  
[_]Concurrency: Some reports say that using innodb\_file\_per\_table improves concurrency because there are individual tablespaces.  
[_]I presume nothing has come from innodb\_file\_per\_database. Facebook talked about this back in 2009 (!) but I’ve not seen anything since. [url][Redirecting...](https://www.facebook.com/notes/mysql-at-facebook/hack-of-the-day/165403635932?comment_id=6285127%5B/url%5D)  
[/LIST] Welcome any thoughts on this.