• Resolved Anonymous User

    (@anonymized-23173868)


    Can you clarify what the “cache wp-admin” setting does exactly? It’s under the object cache section, so I assume it’s caching some kind of DB request but how does it work exactly? What is cached and for how long? I had it turned on and certain transients I was setting using the “set_transient” function were not expiring properly.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support litetim

    (@litetim)

    Short answer: will use object cache to get/store admin data.
    Small description: https://docs.litespeedtech.com/lscache/lscwp/cache/#cache-wp-admin

    Thread Starter Anonymous User

    (@anonymized-23173868)

    Yeah I read that but it was pretty generic. Why did using set_transient not work properly? I checked things out and the transient did not have the expiration set. It said “persistent”.

    Plugin Support litetim

    (@litetim)

    set_transient uses the database which can become a bottleneck very fast if the site is visited.
    Instead of using MySQL/Maria DB we use object cachce libraries(Redis, Memcache) which are faster and can support more traffic.

    Thread Starter Anonymous User

    (@anonymized-23173868)

    So you just bypass the DB and set the value directly in Redis and ignore the expiration? Seems like that WP-Admin setting should be toggled off by default.

    • This reply was modified 1 year, 2 months ago by Anonymous User.
    Plugin Support litetim

    (@litetim)

    Depends on your use: If you need data to be always non cached, I would turn it off 🙂

    If you turn it OFF, please turn ON this setting: https://docs.litespeedtech.com/lscache/lscwp/cache/#store-transients, It will allow transients to be stored.

    Thread Starter Anonymous User

    (@anonymized-23173868)

    OK so I think I understand now after some testing. My object life is set to 360 seconds.

    With WP-Admin set to on, it bypasses the DB and sets thing directly in Redis. Using this method, I am experiencing issues with expired data. Why is that expired transient not getting cleared out of Redis after 360 seconds?

    With WP-Admin set to off and Store Transients turned on, the transient still gets stored in the database before it then also gets put into Redis.

    For both methods, it appears that the expiration I set in the set_transient function is ignored and the “Default Object Lifetime” value is used instead for both methods. I assume this is due to the differences of how set_transient expiration works and the set method for Redis.

    Is this all correct?

    Plugin Support litetim

    (@litetim)

    @thekendog pretty much on point
    I cannot guarantee the expiration is working as you wrote, but you understood the functionality 🙂

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

The topic ‘Please Explain “Cache WP-Admin” Setting’ is closed to new replies.