[wp-trac] [WordPress Trac] #32264: wp_enqueue_media() is slow on large sites

WordPress Trac noreply at wordpress.org
Fri Jul 17 15:51:32 UTC 2015


#32264: wp_enqueue_media() is slow on large sites
-------------------------------------------------+-------------------------
 Reporter:  philipjohn                           |       Owner:  rhurling
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  Awaiting
Component:  Posts, Post Types                    |  Review
 Severity:  normal                               |     Version:  3.9
 Keywords:  good-first-bug has-patch needs-      |  Resolution:
  testing                                        |     Focuses:
                                                 |  performance
-------------------------------------------------+-------------------------

Comment (by mintindeed):

 Replying to [comment:12 westi]:
 > Is there a strong reason to use transients for this instead of just
 having a object cached result that is keyed on something that includes the
 '''last_changed''' value for posts?
 >
 > I guess the only reason would be to try and leverage this for sites
 without a persistent cache backend, I'm not sure I'd want to run without
 one for this many posts however ;)

 My biggest fear with using the caching backend is that we'd be putting
 something into the system that's not clear or visible. A landmine; magic
 functionality that takes place if your infrastructure is set up in a
 certain way. Unless you also add in an admin notice that says "hey, your
 site is pretty big, it's going to run slow unless you implement an object
 cache", then I think it be implemented in a way that any site can take
 advantage of.

 A smaller reason is that dev and QA environments don't always have caching
 (on purpose) and that's where our dev team and product managers spend the
 greatest amount of their time. So we'd have to implement object caching,
 which would change the way our team works and the resources required for
 our dev environments, or deal with a really really slow dev environment.
 Neither one is the end of the world, but enough reason for me to agree
 with using a transient to store this info.

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


More information about the wp-trac mailing list