Pods autoload in options table

  • Resolved Norm Sash

    (@normsash)


    3 years, 3 months ago

    Hi,

    I’ve noticed quite a few _transient_pods_xxxxx entries in the wp options table all set to autoload=yes. This is contributing to a pretty large (> 3MB) options load. Is it really necessary to have all these _transient_pods_ entries autoload? Is there a way to set the autoload value to ‘no’ by defualt for these instead of ‘yes’?

    Thanks,
    -Norm

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    If you have object caching available, this can help reduce transients in the DB.

    You can also use the Pods Alternative Cache plugin: https://www.ads-software.com/plugins/pods-alternative-cache/

    Pods Alternative Cache will segment all of the Pods-related caches and transients so it’s separated from everything else. This can help avoid autoload issues with non-expiring transients as well.

    I will look over Pods itself and adjust things where we have no-expiration transients set so we can reduce this issue in the future.

    Thread Starter Norm Sash

    (@normsash)

    Thanks Scott. I have PHP opcache but not memcached or redis on the server (shared host doesn’t enable memcached). I’ll try the Alternative Cache plugin and see how that goes.

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    Following up — I’ve made adjustments for Pods 2.8 (beta) which help resolve the transients not having expirations (non-expiring transients will autoload).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Pods autoload in options table’ is closed to new replies.