updateTableExists every request, slowing down

  • Resolved Fabian

    (@fabifott)


    7 years, 2 months ago

    I was optimizing my site, and found that updateTableExists get called from wfConfig::loadAllOptions every request.

    It uses a cache there, but adds it to the non persitent group: wp_cache_add_non_persistent_groups('wordfence');
    This limits the cache scope to a single request only.
    Why doesnt wordfence use a persistent cache?

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

  • Hi @fabifott,

    On most sites, it’s a quick check, but on large multi-sites or sites with a slower database server, it can indeed require more time.

    Our development team has been looking into modifying this behaviour however we don’t have a date set for this change yet.

    Using the non-persistent object cache is important for Wordfence because there are some caching plugins that cache things improperly, and this can lead to other issues.

    Thread Starter Fabian

    (@fabifott)

    @wfyann Yes, it was blocking one of my sites for a couple of 100ms. Good to hear that you plan to optimize it!
    I understand the cache issue, its a shame that you actually can’t reliably use the cache anymore.

    Thanks for your reply.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘updateTableExists every request, slowing down’ is closed to new replies.