[wp-trac] [WordPress Trac] #10381: post->ancestors isn't always set
WordPress Trac
wp-trac at lists.automattic.com
Mon Jun 7 13:56:46 UTC 2010
#10381: post->ancestors isn't always set
-------------------------------+--------------------------------------------
Reporter: Denis-de-Bernardy | Owner: ryan
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.1
Component: Cache | Version: 2.8
Severity: normal | Keywords: dev-feedback needs-unit-tests early
-------------------------------+--------------------------------------------
Comment(by Denis-de-Bernardy):
@maorb: the tricky thing is, forcing WP to properly fill the object cache,
when using memcache, makes WP hang a bit; and it makes WP consume an
obscene amount of resources when not.
when I experimented with it, I found that flushing dirty cache items on a
per need basis did a good enough job, considering that it'll end up with
clean data at some point. My own goals were arguably different than yours
though.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10381#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list