• I´ve used W3TC with apache and Nginx. WP-FFPC and WP Super cache only with Nginx. And after see the results with WP Super Cache + Nginx, this is the fastest combination. With apache + fastcgi it was very slow, at leat 14 seconds to load a page. With apc + php-fpm it was normal, about 7 seconds. With WP Super cache + nginx + apc + php-fpm, pages are loaded instantly. In chrome: waiting 112 ms, receiving 92 ms. My website is as fast as google 😀

    Many thanks to WP Super Cache developers. If this plugin were commercial, it´d cost more than 300$ and it´s worth paying. And it´s totally free.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Its really amazing that your website loads in 200 ms. Its really great. Are you using dedicated server or you are using shared server?

    You misunderstand those values.
    200ms is mostly local cache since Super Cache enforces local caching merely everything, while WP-FFPC is only a full page cache and does not touch for example images.

    Thread Starter darkxer0x

    (@darkxer0x)

    @download Converter 200 ms is in receiving html, of course. The whole page is between 1 second and 2. You can try yourself in http://www.feldy.es. The website is in spanish, but you can go to “Catalogo”, and inside there there are a lot of categories full of pictures.

    @petermolnar 200 ms in receiving html. I was comparing only time receiving html (comparing only page cache). I´m planning to do a full analysis between all the cache systems, because after using W3TC, then WP-FFPC, I used Super Cache and discovered in debug mode that pages were not cached due to woocommerce “DONOTCACHE” policy. As I only use woocommerce for catalog, not for shopping, I deleted that policy. So I´ll do a full analysis comparing all the three systems. Do you think pages were not cached in WP-FPPC due to this policy?

    According to GTmetrix, your home page is 1 MB and it loads in 7 seconds and its good. But you didn’t answer my question. Are you using shared or dedicated server?

    Thread Starter darkxer0x

    (@darkxer0x)

    @download Converter According to GTmetrix, the html loads in 512ms. All the rest: javascripts, images, fonts… loads in 7 seconds the first time. But when you visit the second, third… page, all the rest that load in 7 seconds, are now in cache. So it loads in less than 1 second.

    About your question, it´s neither a shared or dedicated server, is a VPS. You can call it dedicated, but a vps it´s far the power from a dedicated, starting for few memory, few cpus… My VPS was the lowest plan: (2 cpus, 2 GB Memory)

    But you dont need a vps, although it helps, because you can customize all the parameters.

    I´m planning to use Cloudfare, and try minify settings. Although I couldn´t get it working with W3TC (I think there were problems with theme javascripts order). If it works with CLoudfare, I suppose the first load will be much better. Although I don´t worry much about the first taking 7 seconds if you receive the html in half second, and the rest pages are quickly 🙂

    Yes, i am totally familiar with VPS 🙂
    But i think WP super cache works excellent too and changing it to W3TC can not speed up your website a lot. And as you see, W3TC is not compilable with wordpress 3.6.1 🙁

    Have you tried using WP-FFPC with the nginx+memcached combination or just the plain install itself?

    Thread Starter darkxer0x

    (@darkxer0x)

    I tried WP-FFPC with nginx + apc + memcached. But I´m not sure pages were cached. When I have time I´ll try again without the policy DONOTCACHE

    WP-FFPC: Please try the PHP -> Memcached engine and add the nginx -> memcached lines recommended on the plugin settings page and try that as well.

    In this case all the generated content will be accessible for nginx with it’s memcached module, meaning you’re leaving the whole PHP loop out when serving the generated content up until the time cache expiration time.

    I do not think the DONOTCACHE flag had any affect on the system until it’s implemented in some really nasty way ( for example a contantly changing tag in the url ).

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘WP Super Cache Nginx’ is closed to new replies.