Some transient caches never deleted

  • kwisatz

    (@kwisatz)


    9 years, 7 months ago

    I’ve written a plugin that makes extensive use of transient caching to … well temporarily cache quite copious amounts of data. The transients are defined to expire after 1200 seconds.

    According to the Transients API, the transients should get deleted LATEST when they expire, but can be deleted anytime before that.

    However, in our case, I have found that some transients, when W3TC is enabled, are never deleted. Any ideas what could be causing this and how I could provide more information that would allow all of us to understand what is going on?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Scott Hartley

    (@destac)

    9 years, 7 months ago

    Are you using the object cache if so try disabling it and only use it with a form of memory caching.

    Thread Starter kwisatz

    (@kwisatz)

    9 years, 7 months ago

    No, object cache is disabled since we had problems with that before. And we also stumbled on the php-apc bug that would crash our web-server. (long-standing bug in Debian an derivatives)

    We have browser, page and database cache enabled.

    Kimberly

    (@amiga500)

    9 years, 7 months ago

    Sadly, my experience in database caching is limited and so is using the transient api so forgive my ignorance. I’m always eager to hunt down new w3tc bugs. So I am curious, don’t transients get stored into the database usually? I am just wondering if the database cache lifespan setting of w3tc is running longer than your transient expire or if a Varnish-like cache server is roaming around your setup. If that is how it works. I will make my way into the transient API library and its w3tc connection in a few days — still dealing with other w3tc code at the moment.

    Regards,
    Kimberly

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Some transient caches never deleted’ is closed to new replies.