WordPress’ default dumping ground for all data related to posts (and custom post types) is in post meta. When there’s a lot of meta data, it starts to strain your server performance and resources in ways you may not have realized.
I’ll go through a real-world example of too much meta-data being stored with a post, some hacks to avoid problems, and some better solutions using the meta data API. I’ll explain how you can easily move data, even if your site has already been designed, developed, and deployed.
Use less memory, handle more concurrent visitors, and speed up page loads by only loading what you need, when you need it.