3 ms·

I wish we saw some specifics of those tweaks-to-the-limit. This post is vague and advertisey IMO. It reads to me as "I might be throwing money out of the window

by pestaa 15y ago

I wish we saw some specifics of those tweaks-to-the-limit. This post is vague and advertisey IMO. It reads to me as "I might be throwing money out of the window, but I'm fed up with dealing with a critical part of my online presence." Shouldn't switching to Nginx be the very first step? Enabling gzip the second, copying assets to a CDN the third? 1024 Mb is a plenty of RAM to keep every post in memory, too. If you have the resources to outsource non-critical parts of your business, good for you.

patio11 15y ago
I thought I was fairly explicit: I previously had nginx proxying to Apache2, using WPSuperCache and a few rewriting rules to serve all static content and the vast majority of pageviews without hitting Apache. Cache headers were set and quite generous, static content was split over multiple subdomains (and served directly by Nginx). I had manually edited the WordPress theme to fix inefficencies with how they bundled CSS and Javascript. Gzip on, images crunched when I remembered to do so, yadda yadda yadda. (A lot of this work had to be repeated every time I switched themes, so I'm not entirely sure it was all up on the most recent one, but I've done it three times at least.) Trust me: I put probably high four figures of engineering time into solving this problem "for free."
- deleted 15y ago
  [deleted]
- pestaa 15y ago
  I believe you put the time in and I would never doubt your (or anybody else's) capability to optimize a site. So it was really just me reading something between the lines that is not there, or the post sounded like "the site was down when I published something... it kept on for several months... then I installed this... it was still slow... then I installed that...". There's absolutely nothing wrong with outsourcing your blog. It just didn't seem justified.
  - scott_s 15y ago
    There's absolutely nothing wrong with outsourcing your blog. It just didn't seem justified. In what way? I thought Patrick clearly explained that maintaining it himself had become a time sink. Hence, he hired competent people to do it for him.
- awesomesauce555 15y ago
  Why use apache at all? Why not just serve it all with nginx?
  - patio11 15y ago
    Long story. My blog is the most trafficked site I run (well, exclusive of BCC) but I have about 15 sites on that server. One of them has a hard dependency for Apache. Moving Apache to 8080 and putting Nginx on 80 got me going with only about an hour of configuration tweaking, but doing the blog totally with Nginx would have required spinning up a new server entirely.
deleted 15y ago
[deleted]

by pestaa 15y ago

patio11 15y ago

I thought I was fairly explicit: I previously had nginx proxying to Apache2, using WPSuperCache and a few rewriting rules to serve all static content and the vast majority of pageviews without hitting Apache. Cache headers were set and quite generous, static content was split over multiple subdomains (and served directly by Nginx). I had manually edited the WordPress theme to fix inefficencies with how they bundled CSS and Javascript. Gzip on, images crunched when I remembered to do so, yadda yadda yadda. (A lot of this work had to be repeated every time I switched themes, so I'm not entirely sure it was all up on the most recent one, but I've done it three times at least.) Trust me: I put probably high four figures of engineering time into solving this problem "for free."

deleted 15y ago
[deleted]
pestaa 15y ago
I believe you put the time in and I would never doubt your (or anybody else's) capability to optimize a site. So it was really just me reading something between the lines that is not there, or the post sounded like "the site was down when I published something... it kept on for several months... then I installed this... it was still slow... then I installed that...". There's absolutely nothing wrong with outsourcing your blog. It just didn't seem justified.
- scott_s 15y ago
  There's absolutely nothing wrong with outsourcing your blog. It just didn't seem justified. In what way? I thought Patrick clearly explained that maintaining it himself had become a time sink. Hence, he hired competent people to do it for him.
awesomesauce555 15y ago
Why use apache at all? Why not just serve it all with nginx?
- patio11 15y ago
  Long story. My blog is the most trafficked site I run (well, exclusive of BCC) but I have about 15 sites on that server. One of them has a hard dependency for Apache. Moving Apache to 8080 and putting Nginx on 80 got me going with only about an hour of configuration tweaking, but doing the blog totally with Nginx would have required spinning up a new server entirely.

deleted 15y ago

[deleted]