jb_transient_concat_paths_ transients (too many!)

  • Resolved pjsgsy

    (@pjsgsy)


    1 week, 3 days ago

    So I am trying to troubleshoot slower than expected inserts and updates into the wp_options table.

    I checked the number of options. Quite a few. I have 8,741 _transient_ entries. Wow, I thought. Start looking at them. 8,685 of them appear to be related to jetpack boost. Perhaps related to javascript processing.

    They all look like this

    jb_transient_concat_paths_0xxxxxxx

    With a rather large values (in terms of storage size). Almost 2k.

    This does seem detrimental to performance. Kind of ironic given this is a performance plugin ??

    Other than disabling boost, is there anything that can be done to fix this? I am assuming it is normal behaviour for this product, but if not, please let me know how I might go about resolving it.

    Thanks.

    • This topic was modified 1 week, 3 days ago by pjsgsy.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Adnan Haque (a11n)

    (@adnan007)

    Hi @pjsgsy !

    The specific transient get’s created for each combination of css/js assets your site loads on different pages. This specific transient represents one set of files loaded by pages on your site.

    The number of items (more than 8000) is unusually high. There might be a plugin/configuration that’s dynamically causing new combinations of CSS or JS files. It should stop if you disable the modules “Concatenate JS” and “Concatenate CSS”.

    If you want to investigate further and get to the root of the issue, try looking into different pages and see if the CSS or JS filenames or their order, change on every page load. Please let us know if you find anything.

    Thread Starter pjsgsy

    (@pjsgsy)

    I’ll try disabling them one at a time. Will the transients automatically be deleted?

    Plugin Author Adnan Haque (a11n)

    (@adnan007)

    The transients will only delete on plugin uninstall. So, you can uninstall(delete it completely) and install it again to clean it up.

    Enabling them one at a time can be a good way to check if it’s JS or CSS specifically. But, it will not be a quick test as these transients would generate as people visit your site. The way I would approach it:

    1. Re-install Boost and have both modules disabled for a day. The duration can be shorter if your site has tons of visitors. This step would be our control sample. We should see jb_transient from other features but no _concat_paths.
    2. Re-install Boost and have one of the Concatenate modules enabled. Leave it like that for the same duration of time.
    3. Re-install Boost, disable the active Concatenate module, and activate the other one. Leave it like that for the same duration of time.

    Based on it, you might be able to pin point if it’s one module or the other. But, it won’t tell us what’s actually causing the problem.

    Thread Starter pjsgsy

    (@pjsgsy)

    OK, thanks. It’s acting weird at the moment!

    I’d tried to disable the CSS and Javascript options. Thought this had taken, but I could not de-activate the plugin. Just goes back to the plugin page after worpdpress says it has been deactivated, but it’s still activated. Check the settings. CSS contact is still on. You try to turn it off, it stays there for 1 second, then the toggle slips itself back on! Go to plugins list, click deactivate. WP again say’s it has been deactivated, but it does not – Still listed as activated and running.

    Don’t want to assume too much as I do not want to break the site, but can I just rename the plugin folder, then how do I clean this mess up neatly given the proper uninstall does not want / seem to run.

    Thanks.

    Plugin Author Adnan Haque (a11n)

    (@adnan007)

    There is probably a PHP error during uninstall. Another potential issue could be that the uninstall is timing out while deleting the transients since there is so many of them.

    Can you check your PHP error log and share if you see any relevant errors? I would suggest deleting the transients manually. But, since the module is not turning off now, I wouldn’t recommend that.

    Please reach us out at https://jetpack.com/contact-support/?rel=support&hpi=1 and mention this thread. We’d like to take a closer look at your site.

    Thread Starter pjsgsy

    (@pjsgsy)

    OK, thanks. I have the php Error log on, but no new errors appear when I try to deactivate it. I’ll reach out to support. Thanks.

    Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @pjsgsy,

    Thank you for contacting via email. I’m going to close this thread and we’ll continue there.

    Thank you!

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