When running cat /proc/meminfo, you get these 3 values at the top:
I use Chromium and have problems with the DNS not being cached for the time that I would expect. Take the example.com domain. According to the DNS settings, this domain should be cached for another 26151 seconds:
Is there a generic way to support caching plugins? For example to set a flag after you update an option that caching plugins watch?
Lets say you are doing an update_option() and because of some temporary network glitches updating the value in Redis/Memcached fails and you end up with a stale cache for a specific option key. The core APIs does not seem to care about the response from wp_cache_set() and they move forward with the rest of the process. Then the subsequent updates could delete or revert that option value in DB and that could have major consequences for the app depending on what that option value is used for. How do you handle this? How is this handled in large-scale WP setups? Anything that can be improved in core?
Update my child theme every time the parent theme is updated to change a version string in style.css (e.g. @import url('../twentythirteen/style.css?ver=NEW_VERSION');). This creates an unnecessary and annoying link between parent theme version and child.
I’m looking for a definitive answer here. When object caching is enabled, where do options and transients end up living?
I was reading over some best practices from 10up and they mention setting these two flags to false in a WP_Query ( depending on what you’re querying ):
I am trying to use get_transient() method in my WordPress, I have read the document and seems like I am doing what has been described in the docs.
I have a site with tons of posts hundreds/thousands of which have YouTube videos embedded. Most use the default youtube_url format and the actual embed code is stored in the oEmbed postmeta fields.