WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #32052, comment 7


Ignore:
Timestamp:
04/22/2015 02:08:32 PM (4 years ago)
Author:
nicofuma
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #32052, comment 7

    initial v1  
    1 I missed that the PO/MO libraries shouldn't have any WordPress dependencies, sorry. So there is a new version of the patch moved to `load_textdomain()` by the way I also moved from the Object Cache API to the Transient API. There are the profiles:
     1I missed that the PO/MO libraries shouldn't have any WordPress dependencies, sorry.
     2
     3Here is a new version of the patch moved to `load_textdomain()`.
     4I also moved from the Object Cache API to the Transient API and here are the profiles:
    25
    36Current state: [https://blackfire.io/profiles/30037359-52be-4bef-8737-f05d40f7c233/graph profile]
     
    58With W3 enabled (and its disk Object Cache strategy): [https://blackfire.io/profiles/c2904256-f0e4-470b-b296-2250b013aac6/graph profile] [https://blackfire.io/profiles/compare/389044c7-920b-4e36-aea0-eba02568cc65/graph comparison with current]
    69
    7 To sump-up: caching this kind/amount of data in database is beneficial but it's faster with an object cache. And thanks to the transient API we use automatically the best caching strategy (db versus object cache).
     10To sump-up: caching this kind/amount of data in database is beneficial (from 47ms to 25ms). Enabling the Object Cache makes things even faster (from 47ms to 8ms).
     11Thanks to the transient API we use automatically the best caching strategy (db versus object cache).