6 ms·
In defense of anyone managing WordPress, its database schema is not well-normalized or organized (last I checked, it still had something like 6 tables). That s
by smt88 6y ago
In defense of anyone managing WordPress, its database schema is not well-normalized or organized (last I checked, it still had something like 6 tables).
That scenario (in general, not referring specifically to WP anymore) makes database indexing/optimization much more expensive at webhost scale, because you potentially have columns that range in size from empty to 1MB.
That's why most WP users have gone deep down the rabbithole of view-level caching, because optimizing an uncached result is so much harder in that environment.
- jamesponddotco 6y agoOh, I agree, optimizing MySQL for WordPress is a constant battle, with plugins and themes not handling the uninstallation process at all, and leaving huge amounts of data inside the wp_options table with autoload = on, for example, or the expensive queries that WordPress itself make — Elasticsearch and object caching are big help on this one in particular. But if you call yourself a managed WordPress hosting company and your marketing material says your entire stack is optimized for WordPress, you should be held to higher standards than a shared hosting company like HostGator, for example.