Performance Killer. Incompatible with Varnish and Server-Side Caching

  • Dan Knauss

    (@dpknauss)


    9 years ago

    This plugin puts a high demand on server resources. It also sets and updates a cookie on every page of your site. This prevents server-side caching/accelerators like Varnish from working. Since the top managed WordPress hosts use Varnish or similar server-side caching, use of this anti-spam method is not a small drawback.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WebberZone

    (@webberzone)

    The plugin isn’t designed to set any cookie. The tracking updates the DB directly.

    It’s designed to bypass a cache since that’s the only way to get the tracking to work. I’m not sure having the code cached will get it to track. As usual, I’m happy to hear solutions to improve the plugin, particularly in performance areas.

    However, in terms of performance, many users have reported this piece of code in the functions.php works because it doesn’t load the whole WordPress backend (probably that’s what sets the cookie)

    https://gist.github.com/ajaydsouza/e4637ebb9df9158fc5a9

    Thread Starter Dan Knauss

    (@dpknauss)

    That is causing a PHP session cookie to be set which has the effect I described, depending on how the server is configured.

    Disregard my mention of anti-spam methods; I was too-hastily pasting this comment here as well as several other plugins that I’ve identified as disruptive to server-side caching.

    Plugin Author WebberZone

    (@webberzone)

    Does the PHP session cookie set if you use the code I showed above in the gist?

    Also, I’d be curious to see what your finding is in terms of performance.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Performance Killer. Incompatible with Varnish and Server-Side Caching’ is closed to new replies.