[wp-trac] [WordPress Trac] #57683: Improve performance of mysql2date

[WordPress Trac]

#57683: Improve performance of mysql2date
--------------------------+-----------------------------
 Reporter:  spacedmonkey  |       Owner:  (none)
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Date/Time     |     Version:  0.71
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  performance
--------------------------+-----------------------------

Comment (by Rarst):

 I pondered such before, but I am generally skeptical of "optimizing"
 options call. It becomes a caching system for a caching system and
 introduces a lot of uncertainty about getting actual option values over
 something stuck in a bespoke cache somewhere.

 I think the safe 50% win here could be to drop mysql2date calls (the date
 formats are fixed so there is no appeal to its crazy input edge cases) in
 favor of plain PHP with a single wp_timezone() call.

 Is the trace crop from a complete themed page load or truncated to just
 post loop or something? Would seem tad high for me if former, but usual
 trace breakdowns aren't on top of my head right now (Blackfire removed
 their free plan, not readily set up for profiling :\ ).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57683#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform