[wp-trac] [WordPress Trac] #22844: random_seed transient is autoloaded with no reason

[WordPress Trac]

#22844: random_seed transient is autoloaded with no reason
--------------------------+------------------------------
 Reporter:  mark-k        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Performance   |     Version:  3.4.2
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by nacin):

 When transients were implemented in 2.8, the argument (as far as I know —
 I was not quite yet involved) was that a transient without an expiration
 was likely going to be fairly frequently needed, thus we should autoload
 it and avoid the query. Yes, it was transient data, but it's still data we
 need regularly until it decides to go away. Transients with expirations
 didn't really fit that mold.

 Based on where to draw the line, should *any* transients be auto-loaded?
 The other transients that are autoloaded (having no expiration are) are
 doing_cron, update_core, update_plugins, and update_themes. These
 transients can be needed at pretty much any time, whenever WordPress is
 executing. Other transients, like API results (popular importers, browse
 happy, credits, themes feature list, plugins tag list), are only needed in
 limited, targeted situations. Which shoe fits random_seed?

 It is worth noting that random_seed used to be an option, but was
 converted to a transient. Generally, options that became transients did
 not have an expiration, because they were "transient" but not necessarily
 something that should ever need to expire.

 We've spoken about implicit expirations for DB transients too — #20316.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22844#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software