[wp-trac] [WordPress Trac] #14558: Separate Database Table Support for Custom Post Types

WordPress Trac noreply at wordpress.org
Thu Sep 5 04:24:10 UTC 2019

#14558: Separate Database Table Support for Custom Post Types
 Reporter:  rahul286           |       Owner:  (none)
     Type:  enhancement        |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Posts, Post Types  |     Version:
 Severity:  normal             |  Resolution:  wontfix
 Keywords:                     |     Focuses:

Comment (by pento):

 Right, I see. For most uses, MySQL is the fastest option for what you're
 describing. It's pretty good about allowing a large number of concurrent
 reads, even while writing data. Retrieving a single post by ID, for
 example, is only a few ms, you may be able to shave off a 1-2 ms by adding
 memcached in this instance, but it's not really worth it.

 Once you scale beyond MySQL's limits, the idea is to add existing tools in
 front of the database. MySQL remains the definitive source, and then you
 have various caching layers which hold objects, rather than DB rows. You'd
 store an entire post, with postmeta in memcached, saving multiple queries.
 In front of that, you'd have a HTML cache, which caches sections of HTML
 pages, or even entire HTML pages.

Ticket URL: <https://core.trac.wordpress.org/ticket/14558#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list