In most cases, you don’t really need to think about the storage type you choose when creating a Pod. But if you’re curious as to what the differences are, this comparison is for you.
Note: We’re going to be re-running the tests below against latest version of MySQL soon, let us know if you’d like to help.
Contents
Availability
CONTENT TYPE | META | TABLE |
---|---|---|
Post Types | ✅ | ✅ |
Taxonomies | ✅ | ✅ |
Media | ✅ | ✅ |
Users | ✅ | ✅ |
Comments | ✅ | ✅ |
Advanced Content Types | No | ✅ |
Database Impacts (from Pods 1.x testing)
DATABASE IMPACT | META | TABLE |
---|---|---|
JOINs per extra field in Query | Yes | No |
Average Index Length per field | 31.69 bytes | 0.7168 bytes |
Average Data Length per field | 72.9 bytes | 32.4 bytes |
MySQL rows per item (Y = # of fields) | 1 x Y | 1 |
MySQL ALTER TABLE when adding / removing fields | ❌ | ✅ |
DB definitions per field No CAST() needed | ❌ | ✅ |
Database Testing (from Pods 1.x testing)
Examples assume 50k items with 20 custom fields.
DATABASE TEST | META | TABLE |
---|---|---|
JOINs for Query filtering by 20 custom fields | 20 | 1 |
Index Length | 31,690,752 bytes | 716,800 bytes |
Data Length | 72,800,000 bytes | 32,400,000 bytes |
MySQL rows | 1,000,000 | 50,000 |