4 ms·

P64 Sysadmin here: We are using heavy caching, on WP and also browser-side. It's still not enough. We previously used Cloudflare, which obviously fixes most of

P64 Sysadmin here: We are using heavy caching, on WP and also browser-side. It's still not enough. We previously used Cloudflare, which obviously fixes most of these problems, but people in these types of circles tend to get pissy about CF.

lallysingh 6y ago
I wonder if you can serve directly on a different domain and put CF on the primary?
deleted 6y ago
[deleted]
spurgu 6y ago
PHP 5.4..? I'd recommend setting up WP Super Cache (which you're using now) to serve static HTML files (not sure what caching method you are using). Then you need to configure Apache (or switch to nginx) to actually look for those files, otherwise the plugin won't do much (it generates PHP files by default which are taxing on the server). Another option would be to switch to the Cache Enabler plugin (along with Apache or nginx configuration) - static HTML page caching as simple as it gets. Oh and upgrade PHP. Edit: For Cache Enabler, check suggested advanced configs at https://www.keycdn.com/support/wordpress-cache-enabler-plugin https://www.keycdn.com/support/wordpress-cache-enabler-plugi... Edit2: CF would just by default cache your CSS/JS, wouldn't really solve the issues you're experiencing (most likely heavy PHP/MySQL load due to poorly configured caching). That said I haven't looked into the site that much, might be that you have a lot of portions of the site that can't be properly cached but then again most users shouldn't need to be logged in so doubt it.
- MartijnBraam 6y ago
  since it's a webshop it will mostly be cache misses anyway for the static generated pages, not sure that will help a lot.
  - spurgu 6y ago
    Yeah that was my only reservation, but the per-user customisation shouldn't be an issue unless you're logged in or have stuff added to the cart, so a general spike in traffic shouldn't (theoretically) affect it.
- fireTwoOneNine 6y ago
  Trust me, PHP 5.x is going to be one of the first things to go in a few days. Moving to PHP 7 should fix many of our issues in one go -- I hope. Along with a move to nginx (which the rest of our web infrastructure already uses). There's a long story as to why all this hasn't be done previously. I'll look into changing the caching once we're over the worst of this. Forgive me if I don't want to make significant changes during a massive traffic spike. ;)
  - spurgu 6y ago
    Haha, of course. :) Hope it turns out well!
cookiengineer 6y ago
Maybe it makes sense to load off as much as possible from the static assets to another host, e.g. gitlab pages as "static.pine64.org" or similar? I mean, most of the WP related assets do not have to be served through PHP necessarily, so they can free up some connections very easily. If you need help with the webdev side of things to optimize/simplify more on the CSS/JS side, I'd love to help out in this project.

lallysingh 6y ago

I wonder if you can serve directly on a different domain and put CF on the primary?

deleted 6y ago

[deleted]

spurgu 6y ago

PHP 5.4..? I'd recommend setting up WP Super Cache (which you're using now) to serve static HTML files (not sure what caching method you are using). Then you need to configure Apache (or switch to nginx) to actually look for those files, otherwise the plugin won't do much (it generates PHP files by default which are taxing on the server). Another option would be to switch to the Cache Enabler plugin (along with Apache or nginx configuration) - static HTML page caching as simple as it gets. Oh and upgrade PHP. Edit: For Cache Enabler, check suggested advanced configs at https://www.keycdn.com/support/wordpress-cache-enabler-plugin https://www.keycdn.com/support/wordpress-cache-enabler-plugi... Edit2: CF would just by default cache your CSS/JS, wouldn't really solve the issues you're experiencing (most likely heavy PHP/MySQL load due to poorly configured caching). That said I haven't looked into the site that much, might be that you have a lot of portions of the site that can't be properly cached but then again most users shouldn't need to be logged in so doubt it.

MartijnBraam 6y ago
since it's a webshop it will mostly be cache misses anyway for the static generated pages, not sure that will help a lot.
- spurgu 6y ago
  Yeah that was my only reservation, but the per-user customisation shouldn't be an issue unless you're logged in or have stuff added to the cart, so a general spike in traffic shouldn't (theoretically) affect it.
fireTwoOneNine 6y ago
Trust me, PHP 5.x is going to be one of the first things to go in a few days. Moving to PHP 7 should fix many of our issues in one go -- I hope. Along with a move to nginx (which the rest of our web infrastructure already uses). There's a long story as to why all this hasn't be done previously. I'll look into changing the caching once we're over the worst of this. Forgive me if I don't want to make significant changes during a massive traffic spike. ;)
- spurgu 6y ago
  Haha, of course. :) Hope it turns out well!

cookiengineer 6y ago

Maybe it makes sense to load off as much as possible from the static assets to another host, e.g. gitlab pages as "static.pine64.org" or similar? I mean, most of the WP related assets do not have to be served through PHP necessarily, so they can free up some connections very easily. If you need help with the webdev side of things to optimize/simplify more on the CSS/JS side, I'd love to help out in this project.