4 ms·

The title is wrong. Like you said in article, it's not a WordPress server but only a nginx serving static content. Only 2 persons hit PHP on your Pi, you when

• akavlie 14y ago
  Caching plugins are a prerequisite for Wordpress to survive heavy traffic though, even on much more powerful servers. Anyone who knows what they're doing is using one.
  • Nikkau 14y ago
    I know and every regular readers of HN knows, it's my point. Pi can serve statics, ok, we all already know it, what's the news?
• InclinedPlane 14y ago
  This is how caching works in the real world. Everywhere. For a CMS delivering mostly static data this is a perfectly fine way to do it.
  • hosay123 14y ago
    Not quite everywhere. When you have enough traffic, the load spikes resulting from putting cache generation in the user path becomes seriously painful, so often a separate process is responsible instead. (Imagine 5,000 threads all deciding they want exactly the same data at exactly the same time, then trying to write it to exactly the same location. Now imagine 50,000 more threads trying to do exactly the same thing because of the delays caused by the first set. Now imagine your web site is down and your mobile phone is ringing)
    • Firehed 14y ago
      Yes, the thundering herd problem. While the site may be briefly less responsive, if the traffic is all to a single piece of content as long as one of them goes through you'll end up with the content in cache and then the load immediately drops. The bigger problem is when your entire cache is cold (ex. memcached was restarted) and there's a ton of traffic to lots of different content. A single piece of content should not be that crippling, unless it's stupidly-slow to render and cache.