Make WordPress Core

Changes between Initial Version and Version 20 of Ticket #26638


Ignore:
Timestamp:
09/12/2018 03:40:08 AM (5 years ago)
Author:
ocean90
Comment:

Going to close this as a wontfix for now since the patches don't comply with how core loads translations anymore. See #34114 for history. Feel free to reopen if someone has a solution which doesn't copy most of get_translations_for_domain() into each translate function and still has a noticeable performance improvement.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26638

    • Property Status changed from new to closed
    • Property Focuses performance added
    • Property Summary changed from [Patch] Performance Increase in l10n (9-12%) to Performance Increase in l10n (9-12%)
    • Property Version changed from trunk to 2.9
    • Property Milestone changed from Awaiting Review to
    • Property Keywords has-patch needs-testing reporter-feedback dev-feedback added
    • Property Resolution changed from to wontfix
  • Ticket #26638 – Description

    initial v20  
    1 While doing some writing on profiling I choose Wordpress as my example application and wrote a small patch that in my testing boosts performance of index.php by 9-12% (with the dataset from my 6 year old blog, ~250 posts, lots of plugins and extra stuff).
     1While doing some writing on profiling I choose WordPress as my example application and wrote a small patch that in my testing boosts performance of index.php by 9-12% (with the dataset from my 6 year old blog, ~250 posts, lots of plugins and extra stuff).
    22
    33This performance increase is found by making a small change to the way `translate()` works, effectively cutting out the use of the `NOOP_Translates` class.