WordPress Caching with Nginx and Redis • Hacker News Board

Re: WordPress Caching with Nginx and Redis

#21

Post by tmzt » Sun, May 12, 2013, 9:01 AM UTC

I 'm curious why you are still invoking PHP and not serving the cached page directly from Redis with Nginx.

I believe that detecting the prescense of cookies, HTTP methods and and request paramters are all supported using the buitlin "if" block and standard HTTP module variables.

Re: WordPress Caching with Nginx and Redis

#22

Post by callumjones » Sun, May 12, 2013, 9:19 AM UTC

Since when has memcached been hard to configure, most times I've left it in either the default settings or upped the memory allocation. If you're going to treat Redis like a cache you should really be looking at memcached.

"best of all, it’s open source" -- Open Source should never be the tickbox on a feature set that wins over another product. Look what the product provides now and into the future with the less work -- just because you can change or view the source code doesn't mean it's going to grow with you.

Re: WordPress Caching with Nginx and Redis

#23

Post by zzzeek » Sun, May 12, 2013, 4:08 PM UTC

icelancer wrote: post #7

zzzeek wrote: post #3

if you're technical enough to set up Redis I'd think you're technical enough to ditch Wordpress silliness and just publish statically.

Setting up redis very simple. Ditching WP isn't.

I found ditching WP very simple, and unlike adding redis, you can even ditch your host and stick your files on S3. My quality of life improved dramatically once I didn't have to keep patching wordpress, breaking all my plugins every 6 weeks, and still getting hacked once in awhile anyway.

Re: WordPress Caching with Nginx and Redis

#24

Post by zzzeek » Sun, May 12, 2013, 4:09 PM UTC

olapersson wrote: post #4

zzzeek wrote: post #3

if you're technical enough to set up Redis I'd think you're technical enough to ditch Wordpress silliness and just publish statically.

But you might run the blog with someone who isn't. Or be running the blog for someone else. Setting up varnish is another option that's likely even better (didn't read the details of the post, but it looks like it always hits a php script to get the cache).

I think integrating wordpress-like administration systems with static publishing systems should be a major goal. That's how movable-type used to work in the old days, and it was great. Now that we have client-side plugins like Disqus for dynamic interactivity features, there's no need for published content to be dynamically rendered. It's all downside and no upside, other than, "wordpress exists".

Re: WordPress Caching with Nginx and Redis

#25

Post by wyck » Sun, May 12, 2013, 4:55 PM UTC

pavs wrote: post #13

vegardx wrote: post #11

Earlier quoted context omitted.

You are talking about two different things here. Memcached is a memory store, while APC is a opcode cacher. W3 seems to be a plugin for Wordpress that serves pre-rendered pages using some mod_rewrite trickery.

I meant under W3 there are more than one option for cache storage. http://i.imgur.com/OjbyvF2.png and APC is faster than memcached in a single server environment http://stackoverflow.com/questions/1794342/memcache-vs-apc-f... . I assume that most people using php most likely already have apc installed (or they really should).

Most people on WordPress and/or using PHP are on shared servers and thus cannot use APC.