New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Because you love apache doesn't mean other people cannot use other type of webserver and you can mad at them if they using it lol. It's just everyone personal preference. Just saying.
I'm not the one going on every Apache related thread and saying "use nginx it's better".
Reminds me of that movie Idiocracy.
Brawndo, it's got what plants crave, it's got electrolytes.
Haha, me and the wife's favorite of all time. I'm positive that it's a prophecy.
Okay, your win sir.
I would highly recommend installing Debian 7, Nginx, PHP5 (DotDeb), PHP5-FPM. Enable fastcache and get the Nginx Helper plugin in Wordpress to purge cache.
I have a 128MB VPS running this and it can handle 10K visitors.
I tried it with Lighttpd. It was easy setup based on the link shared by @nocom. Can you share a step-by-step setup link (I know it cannot be 100% foolproof)? I do not mind experimenting with a couple of options and my own comfort level... So far, I do not feel daunted with lighttpd.
I usually just set it up myself. I'll send you a link in a bit. I need to make it first.
Thanks, will wait for the link and try.
http://evansolomon.me/notes/faster-wordpress-multisite-nginx-batcache/ by Evan Solomon or maybe this http://wpmu.org/wordpress-multisite-wordpress-nginx/, optimize mysql
Enjoy!
http://bit.ly/1fm05ov
Will try in some time and let you know. Thanks
What??? I have run sites that get thousands of uniques a month on 256mb RAM VPS. A demo site will happily run on such a VPS without any trouble at all. And webmin? Webmin takes just 19MB RAM!
Why in the world would you waste 7% of your memory on something that you shouldn't even have to use once it's configured? Also, web servers DO scale and require more memory as they serve more clients, unless you heavily use varnish and that eats your memory too. Doesn't matter what web server, the more clients hit it the more it ramps up resource usage. Yes you can get thousands of visitors on 256mb but it depends a lot on the actual content that you're serving, and a hell of a lot on your robots.txt. I'll bet you also have some cloudflare in there unless your content is very minimal. Some websites absolutely cannot do that. Depends on the purpose. I focus on the rule and not the exception. I know what the average Wordpress user does and they shouldn't be wasting memory on a 256mb VPS.
Nope no cloud flare and apache as the web server. No caching plugins even. Even static files uploaded to WP were served by php (ms-files.php). And yeah RAM usage goes up as you get visitors but as I said thousands of uniques a month in 256MB openvz on a centos 6 host node is entirely doable. Even with xen or kvm it is doable. You don't know how to optimize apache so you are saying what you are saying.
As far as webmin goes if it's that big a deal you can always shut it down after the initial configuration. But if you can't spare 19MB then you have bigger problems.
Lol that's funny. If you don't have wordpress caching installed you're trolling if at any point you talk about optimization. Unnecessary SQL queries are stupid with high traffic and low memory. Your description is incompatible. You either don't have content or you don't get 100 IPs ever hitting the site at once, and when that does happen your site goes down and you just don't know it.
Run a http://www.blitz.io against your site, and lets see what results you get.
^ This. If you're making SQL queries for every visitor and bragging about how you sustain thousands of visitors on a LAMP install where you're wasting memory, don't tell me I don't know how to do my day job. Just because you haven't been hit by the right bots yet who don't respect your robots.txt, or you have and didn't notice that visitors were being rejected, doesn't mean your hobby project makes you an expert. Optimization for Wordpress STARTS with Wordpress and ENDS with Apache. You don't have to be anyone special to get hit with crazy traffic, you just have to run a Wordpress and eventually show up on the radar for malicious bots. Then you'll sit there and ban full subnets all day (and/or changing your htaccess rules to fit whatever UA string they're using this month) until you get tired of it and learn how to actually optimize a website. Seen it, done it, over and over again.
I don't mean to sound insulting but "You don't know how to optimize apache" is a pretty inaccurate thing to say to the guy who has practically dedicated his life at the moment to doing exactly that one thing.
A few thousand uniques a month is not high traffic and not the level at which you would get 100 simultaneous connections. At this traffic level you would get maybe 10 to 20 simultaneous connections at most.
And doing caching in PHP is a silly idea anyway. It is for those people who don't have root access to their server. If you have access then you should use something like nginx helper plugin that merely leverages Nginx's caching. But again it is not required at the traffic level I am talking about.
To what end? I know I sustained the traffic load I mentioned for around a year and I don't have that VPS anymore.
So you are taking my comment about a few thousand uniques a month and twisting it into surviving a veritable DoS? I never claimed that I could do that with a small VPS and neither is that a requirement for 99% of sites. Now it is you who is talking about the exception rather than the rule.
Like I said, you don't have to be somebody special. Just wait until the bots that you can't control bring down your site. It may not be today, tomorrow, or next month, but they'll kick you down fast and you'll see that your website doesn't scale well and you'll need every resource available just to work to mitigate it when it happens. There is no single rule that will prevent this. The way you prepare for it is by minimizing the impact of traffic on your site, not by dealing with it afterward. Without a caching plugin for Wordpress, you haven't even completed the first step to preparing for this. Apache optimization will not help you. I literally see this happen every single day.
What? How in the world is caching static content a silly idea? Most especially, I'm talking about caching content to avoid a MySQL query for EVERY visitor. That's the first rule of website optimization and it's the first thing that will bring you down with something even as small as Google and Bing hitting you at the same time. Every optimization that you don't make now is a problem later. If you go 6 years without seeing the problem, congratulations, but it's still coming.
A web server should be serving content, not creating it for every visitor. Everyone thinks they're special, like the guy who says "Well I don't advertise my server so no one is going to brute force my SSH on port 22." We all know that's a load of crap. Maybe his IP isn't in a popular subnet, maybe he won't see it happen until next year, but it will happen. How about the guy who says "I don't need to update my Joomla, it's not a popular site" and gets defaced 4 years later? All you need is to be on the internet and you are a target. The question is, do you want to do the work now or do you want to react later?
The sites I am talking about have been up since 2006. Yet to face that problem and it has nothing to do with what I said. Again you are putting in scenarios that 99.9% of people never face.
That is not what I wrote. You've quoted me but ignored what I wrote. I said caching in PHP was a silly idea. Better to do the caching in C code i.e. at the web server level.
It's far more than 0.01% dealing with these things and people should prepare basic and simple optimizations beforehand rather than roll the dice and see if they're one of the fortunate ones who goes unnoticed or not. As far as caching goes, I said content that created SQL queries should be cached so each visitor doesn't generate an SQL query and I stand by that. No matter the traffic level. Opting to make your website slower than it has to be is hardly a value worth clinging to.
Well not in my experience.
Great! The caching I am talking about and which is done at the web server level also saves SQL queries. But again not required for the traffic level I am talking about.
Traffic level definitely determines the level of optimization you do. It takes time, effort and money to optimize so you only do it if you have to. And no one is opting to make their site slower. We are opting out of making it faster because making it faster costs the aforementioned time, effort and money.
Right, and for those who like to keep up with realities, Google did some research on it and it was actually quite interesting.
http://googleresearch.blogspot.com/2009/06/speed-matters.html
After all, how many of us are making web pages with the idea that the viewer doesn't matter? Otherwise I believe the old trend of keeping a journal to be a far more productive use of your time.
What optimization are you talking about? Please be specific. I always optimize apache and mysql. But I don't like WP caching plugins like super cache and total cache for my low to mid traffic sites because they have downsides to them:
Sometimes stale content is served. For example when you change sidebar widgets, update a post, or a new comment is posted it doesn't get reflected on the site right away.
They interfere with other plugins notably ecommerce plugins like woocommerce
Super cache does not work with all permalinks last I checked and this has SEO implications. It works by replicating a directory structure and placing static index.html files so if you have permalinks like example.com/blog/whatever/ it is ok but if your permalink structure is different like example.com/blog/page.html then you can't use super cache without adding a trailing slash to your links. This is a bad thing for SEO. For legacy reasons I have such a permalink structure on one of my sites.
Fixing all the above does require developer time and money or the alternative which is to put up with the downsides. It is easy for a host to say that all users should install caching plugins. This reduces resource usage and saves the host money. But it is not always in the interest of site owners and users.
And FYI see my site's results:
http://tools.pingdom.com/fpt/#!/bNbM2/abdussamad.com
Yes and that is why I said on page 1 that caching in PHP is a bad idea and it is better to cache at the web server level:
But you still have some of the downsides I mentioned above. Stale content being served for instance.
Also another thing is that caching might even be a waste of resources. For example say you only have a few thousand visitors per month to an entire site and for compatibility reasons you can only cache a web page for a maximum of 4 hours. WP nonces for example are only valid for 24 hours. You might find that a lot of web pages just don't get visitors that often so the cache is always stale and a new dynamic page has to be generated every time.
But I have to ask Zen what criteria you use to judge competence? I have been able to squeeze more performance out of a low end VPS than Jarland says is even possible yet you call me incompetent. Is competence being able to install 1 click WP caching plugins? Is that some great skill to be proud of?
Usually i'm just enabling internal wordpress caching. Other than that just using tweaked web server configuration.
Thank you so much for all your responses. For my current project, i have setup Debian minimal 7 (32 bit) with lighttpd and wordpress.
What is the best method of backing up the lighttpd and wordpress so that I can restore the same should something go wrong with the vps container?