_transient_ptk_patterns Autoloaded

  • Resolved Leo Santis

    (@leosantis)


    2 months ago

    This transient is set to autoload on all pages and in my case its size is about 500Kb, and WordPress keeps me warning about such huge size.


    Apparently, it stores a model theme that I use, and not even included the customizations I have implemented on this theme. Even the model pictures are stored into it and that’s the reason of its size.


    Despite of searching on all documentation, I couldn’t find anything related to this transient so I decided to set its autoloaded to off and my board seems to be ok without it.


    Point is, every time Woocommerce is updated, this transient is back on all the pages affecting performance.


    Strange thing about is when my theme needs an upgrade, this transient remains off and only when Woo is upgraded it gets back on.


    Main question is, what’s the real purpose of this transient? What should I expect to see when turned off?
    Why the reason it’s storing such huge info that’s apparently useless.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @leosantis

    Thank you for bringing this issue to our attention. I did some research in our GitHub repo and found two pull requests that could help clarify things for you:

    I’m not entirely certain, but I can certainly share some information that could help clear things up for you:

    1. The transient you’re seeing is related to a new feature in WooCommerce that fetches patterns from the Pattern Toolkit (PTK) API.
    2. The large size (around 500KB) is likely due to the transient storing multiple patterns, including default images. This is designed to improve performance by caching the data locally.
    3. You’re correct that a large autoloaded transient can impact performance. We’ve recently made changes to optimize this process and reduce unnecessary logging.
    4. The transient reappearing after WooCommerce updates are expected behaviour. The update process likely clears the existing transient and recreates it with fresh data from the PTK API.
    5. While the transient stores theme-related data, it’s primarily managed by WooCommerce, which explains why it’s not affected by theme updates.
    6. The availability of these patterns (and consequently, the creation of this transient) is tied to the “Allow usage of WooCommerce to be tracked” setting. If you disable this setting, the patterns and the associated transient should not be created.
    7. We’ve recently made changes to reduce unnecessary logging related to this feature, which should help with performance and log file sizes.

    Recommended Actions:

    1. Check your “Allow usage of WooCommerce to be tracked” setting:
      • Go to WooCommerce > Settings > Advanced > WooCommerce.com
      • If you don’t need these additional patterns, consider unchecking this option.
    2. If you need the patterns but want to optimize performance:
      • Your approach of setting the autoload to “off” is a valid temporary solution.
      • We’re continuously working on optimizing this feature. Ensure you’re using the latest version of WooCommerce.
    3. Monitor your site’s performance. You can use a plugin like Query Monitor to assess the impact of this transient on your site’s performance.
    4. Consider using a caching plugin. This can help mitigate the performance impact of large transients.
    5. If you’re a developer, you can check the status of the pattern-toolkit-full-composability feature flag and disable it if necessary.

    We appreciate your detailed report, as it helps us improve WooCommerce. We’re actively working on optimizing this feature to reduce its performance impact while maintaining its benefits.

    Additionally, for development and custom coding questions, it’s best to ask for insight related to those on either the WooCommerce Advanced Facebook group or the WooCommerce Community Slack. Many of our developers hang out there and will be able to offer insights into your question.

    I wish I could help more, but hopefully, this gets you going in the right direction to get some further insight/information.

    Thread Starter Leo Santis

    (@leosantis)

    Dear @shameemreza, thank you for all of your comments, this gave me a full idea about that and how to handle it.

    Plugin Support Rajesh K. (woo-hc)

    (@rajeshml)

    Hello @leosantis,

    Glad to know that we were able to help.

    Please feel free to reach out if you have additional questions.

    Cheers!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.