WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #17128, comment 15


Ignore:
Timestamp:
01/13/12 21:56:04 (3 years ago)
Author:
Chouby
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17128, comment 15

    initial v1  
    11I observed the same issue. 
    22 
    3 Please correct me if I am wrong, but it looks like every internationalized strings are loaded on every page. Loading the complete mo file on every page could explain such huge difference of performance between English and localized versions. Moreover, as WorPress is growing, the mo file is growing too (for de_DE.mo, it was 296 ko for 2.8, 386 ko for 3.0 and 435 ko now), so this performance issue is growing too. 
     3Please correct me if I am wrong, but it looks like every internationalized strings are loaded on every page. Loading the complete mo file on every page could explain such huge difference of performance between English and localized versions. Moreover, as WordPress is growing, the mo file is growing too (for de_DE.mo, it was 296 ko for 2.8, 386 ko for 3.0 and 435 ko now), so this performance issue is growing too. 
    44 
    55So if my assumption is good, the most optimized solution could be to load only the strings needed for the current page. I am not a specialist of the pomo structure, but I imagine that in the worst case it could mean splitting the current mo file in many small files. Obviously it would be difficult to do and maintain.