3 ms·

I mean, that's exactly the point of caching.

by m-p-3 4y ago

capableweb 4y ago
Yeah but I mean: you can't really say that your homegrown Perl script running on a potato can handle 10k req/s if you put caching in front of it. What you're really saying in that case is that your caching solution can handle 10k req/s, which is fine, but besides the point. Same with Wordpress. Wordpress itself cannot handle that amount of load, which is why you put caching in front of it. Users won't care, I give you that. But if you're talking about how much load a specific software can manage, including putting caching in front of it kind of defeats the point of the conversation.
- tedivm 4y ago
  There's a difference between full page caching like you're describing and in application caching. Most Wordpress caching extensions work internal to the application, not externally by putting something in front of it. With one of the popular extensions you can reduce database calls to basically zero without putting a http cache in front of the application.
  - cnity 4y ago
    I think the implicit point made by GP is to question what the purpose of database calls are to deliver a blog post. If the post were just some HTML and CSS, it should be able to be served with very little processing power. It's unlikely that dynamic template population is needed for blog posts.
    - bornfreddy 4y ago
      > If the post were just some HTML and CSS, it should be able to be served with very little processing power. Actually, with caching - they are. The database is there so that the person writing the blog post doesn't need to be very technical, or maybe so that they don't need to make a special effort just to update some post. In the end everything is about convenience.
- claudiulodro 4y ago
  It doesn't make sense to talk about "how much traffic WordPress can handle" because WordPress is a software that runs on a server. It's like talking about how much traffic nginx "can handle" -- the server setup, hardware, RAM, etc. are key. WordPress running on a potato will handle less traffic than WordPress running on a decent server.

I mean, that's exactly the point of caching.

by m-p-3 4y ago

I mean, that's exactly the point of caching.

Yeah but I mean: you can't really say that your homegrown Perl script running on a potato can handle 10k req/s if you put caching in front of it. What you're really saying in that case is that your caching solution can handle 10k req/s, which is fine, but besides the point. Same with Wordpress. Wordpress itself cannot handle that amount of load, which is why you put caching in front of it. Users won't care, I give you that. But if you're talking about how much load a specific software can manage, including putting caching in front of it kind of defeats the point of the conversation.

tedivm 4y ago
There's a difference between full page caching like you're describing and in application caching. Most Wordpress caching extensions work internal to the application, not externally by putting something in front of it. With one of the popular extensions you can reduce database calls to basically zero without putting a http cache in front of the application.
- cnity 4y ago
  I think the implicit point made by GP is to question what the purpose of database calls are to deliver a blog post. If the post were just some HTML and CSS, it should be able to be served with very little processing power. It's unlikely that dynamic template population is needed for blog posts.
  - bornfreddy 4y ago
    > If the post were just some HTML and CSS, it should be able to be served with very little processing power. Actually, with caching - they are. The database is there so that the person writing the blog post doesn't need to be very technical, or maybe so that they don't need to make a special effort just to update some post. In the end everything is about convenience.
claudiulodro 4y ago
It doesn't make sense to talk about "how much traffic WordPress can handle" because WordPress is a software that runs on a server. It's like talking about how much traffic nginx "can handle" -- the server setup, hardware, RAM, etc. are key. WordPress running on a potato will handle less traffic than WordPress running on a decent server.