Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #57648, comment 13


Ignore:
Timestamp:
02/09/2023 12:13:35 AM (17 months ago)
Author:
flixos90
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #57648, comment 13

    initial v1  
    11@oandregal For next steps: I would suggest to do some profiling on `wp_enqueue_global_styles()` and the code paths it runs, to see where specifically it has become slower than in 6.1.1. Let me know if you have capacity to do that, or if you need help.
    22
    3 Also, could you try to run the Server-Timing metrics approach on your system and share the results you get? One thing that's very odd is that, just in my local WordPress core development environment, I still keep getting that same ''very'' large regression from that function. I'm not sure why, maybe there is some expensive logic in there that somehow only triggers in that specific configuration? I would be curious how that plays out in your core dev environment.
     3Also, could you try to run the Server-Timing metrics approach on your system and share the results you get? One thing that's very odd is that, just in my local WordPress core development environment, I still keep getting that same ''very'' large regression of >400% from that function. I'm not sure why, maybe there is some expensive logic in there that somehow only triggers in that specific configuration? I would be curious how that plays out in your core dev environment.
    44
    5 I'm changing the severity here back to normal, since now that regression is actually not as alarming as originally thought. And honestly, other than that, performance-wise WP 6.2-beta.1 looks great! 🎉
     5I'm changing the severity here back to normal, since now that regression is actually not as alarming as originally thought. And honestly, other than that, performance-wise WP 6.2-beta.1 looks great!