4 ms·

Not using Wordpress to serve static blog content should be a good start. Also running the database, webserver, mail server, etc. off a single machine is just a

by netule 10y ago

Not using Wordpress to serve static blog content should be a good start. Also running the database, webserver, mail server, etc. off a single machine is just asking for trouble.

eropple 10y ago
Wordpress can trivially handle "static blog content" with any of a number of caching plugins. (And you get a lot more out of it, in my experience, than trying to use Jekyll or the like.) nginx, PHP-FPM and APC, your caching tool of choice, done.
- mmagin 10y ago
  And yet after all these years, they've never bothered to roll functionality like that into the base install.
  - eropple 10y ago
    I much prefer, as somebody who uses this stuff pretty heavily, to make the choice of caching particulars myself and to not have to unscrew their defaults. A cache API would be fine, but I'd rather have as few decisions made inside Wordpress as possible.
    - mmagin 10y ago
      I know that attitude well, but really this is a problem that's persisted for years and they have basically acted like it's not their problem, which leaves me unimpressed.
duaneb 10y ago
Wordpress is fine; this is why things like Varnish exist. If it's static content you can generate it by hand and serve it as fast as possible (after initial generation, obviously).
- lucb1e 10y ago
  > Wordpress is fine; this is why things like Varnish exist Sounds like "now you have two problems"? There is plenty of blog software out there but very few are so terribly, terribly slow as Wordpress. I'm pretty sure it's the slowest thing I've ever installed on my server (and uninstalled, obviously). Just use something else and there is no need for caching in the first place.
  - duaneb 10y ago
    Why would the speed of the blog be a problem if it's behind a cache? Just ramp up the ttl entering varnish and purge aggressively on changes; hell, just reboot varnish any time you make a change. Nothing about a cache interface is difficult to work around when your content changes as little as a blog would. If anything, moving to an unproven blog framework is going to cause much more headaches than a worpress blog slowing down for seconds every time you make a post.
lucb1e 10y ago
> Also running the database, webserver, mail server, etc. off a single machine is just asking for trouble. Until five years ago I ran that* on an old 2001 laptop with 128MB RAM, of which about 56MB went to Windows XP. Worked quite fine really. * That, plus FTP server, SMB, DNS, VNC and uTorrent. I think that was all.

by netule 10y ago

Not using Wordpress to serve static blog content should be a good start. Also running the database, webserver, mail server, etc. off a single machine is just asking for trouble.

eropple 10y ago

Wordpress can trivially handle "static blog content" with any of a number of caching plugins. (And you get a lot more out of it, in my experience, than trying to use Jekyll or the like.) nginx, PHP-FPM and APC, your caching tool of choice, done.

mmagin 10y ago
And yet after all these years, they've never bothered to roll functionality like that into the base install.
- eropple 10y ago
  I much prefer, as somebody who uses this stuff pretty heavily, to make the choice of caching particulars myself and to not have to unscrew their defaults. A cache API would be fine, but I'd rather have as few decisions made inside Wordpress as possible.
  - mmagin 10y ago
    I know that attitude well, but really this is a problem that's persisted for years and they have basically acted like it's not their problem, which leaves me unimpressed.

duaneb 10y ago

Wordpress is fine; this is why things like Varnish exist. If it's static content you can generate it by hand and serve it as fast as possible (after initial generation, obviously).

lucb1e 10y ago
> Wordpress is fine; this is why things like Varnish exist Sounds like "now you have two problems"? There is plenty of blog software out there but very few are so terribly, terribly slow as Wordpress. I'm pretty sure it's the slowest thing I've ever installed on my server (and uninstalled, obviously). Just use something else and there is no need for caching in the first place.
- duaneb 10y ago
  Why would the speed of the blog be a problem if it's behind a cache? Just ramp up the ttl entering varnish and purge aggressively on changes; hell, just reboot varnish any time you make a change. Nothing about a cache interface is difficult to work around when your content changes as little as a blog would. If anything, moving to an unproven blog framework is going to cause much more headaches than a worpress blog slowing down for seconds every time you make a post.

lucb1e 10y ago

> Also running the database, webserver, mail server, etc. off a single machine is just asking for trouble. Until five years ago I ran that* on an old 2001 laptop with 128MB RAM, of which about 56MB went to Windows XP. Worked quite fine really. * That, plus FTP server, SMB, DNS, VNC and uTorrent. I think that was all.