I posted our observation on my site: http://www.crazyengineers.com/threa...-world-page-loading-speed-test-results.70941/ and Michael from LiteSpeed replied. Do check it.
What's the problem?Litespeed vs Nginx ??
No problem, just interested in a LiteSpeed vs Nginx comparison to see the pros and cons of each and which gives better performance. Haven't used Apache for 3+ yrs, so comparisons with Apache mean very little to me.What's the problem?
LITESPEED hereby grants You a non-exclusive and
nontransferable license to use the SOFTWARE PRODUCT and documentation on
a computer for which you have paid the corresponding fee. You may not use
the SOFTWARE PRODUCT to host pornographic content.
Well, you won't get a concrete answer about this. Some people can swear by Nginx and others by Litespeed. It really depends how heavy is your software (add-ons, etc`), how many people visit your website, your box specs, and how well you know to configure Nginx.No problem, just interested in a LiteSpeed vs Nginx comparison to see the pros and cons of each and which gives better performance. Haven't used Apache for 3+ yrs, so comparisons with Apache mean very little to me.
Litespeed vs Nginx ??
Don't like leasing software, so I'd be looking at $799 x 2. I think I'll stick with mucking through nginx's config files.What your paying for is convenience.
Don't like leasing software, so I'd be looking at $799 x 2. I think I'll stick with mucking through nginx's config files.
I could see purchasing it if it was a money making proposition, but for a hobby site it's overkill.
OpenLiteSpeed looks promising, but because of some quirks I experienced I couldn't use it.
You could do the same thing with Nginx, purchase one of their support packages and they will tune your server to death... you don't have to move a finger. Not to mention that Nginx Inc. offers a custom Nginx software specifically tuned for performance with additional features not available into free version.If you have the money, and you have a medium-large community, I would defiantly go with Litespeed to save server cost in the long run. With my testing over different configurations, Litespeed performed better, but I haven't had the time to play with Nginx very long.
I'm using Litespeed in the last 6 months or so, and I'm very happy about my decision to purchase a license. Take in account that Nginx doesn't support htaccess if that's important for you (it is for me).
Not if you don't like Apache.Nginx for a hobby site is overkill
Not all sites are about the "money". Some are about providing users with a good experience. Hopefully my forums will take off in a year or two and even when they do, the only income that I foresee coming from them will be a small adsense ad at the footer for registered users and in 2 additional spots for unregistered.Any site generating enough traffic to warrent using Nginx, should also be generating enough income to lease a Litespeed License.
About .htaccess, you should not need this on a modern server with modern software. I don't know how LiteSpeed reads the .htaccess files but if it does it like Apache, then is pretty bad. Apache needs to check EVERY directory in the requested path for the existence of a .htaccess file and if it exists, it reads EVERY one of them and parses it. This happens for EVERY request. You should stop using .htaccess period, is horrible for performance. This is one of many areas where Nginx shines.
I also wonder why companies like Facebook, Wordpress, Github, Cloudflare, Netflix, Intel, etc. don't use LiteSpeed.
I consider myself average Joe .. and learnt both without any problems. Maybe I'm just too humble, or really good at google and reading.Your average Joe end user isn't going to be able to work out how to use nginx, let alone convert rewriterules.
I was referring to the way Apache works, not LiteSpeed:Interesting comments there Floren, you first say you don't know how the web server works, and then make a very generic, and subsequently wrong statement. LiteSpeed caches .htaccess so it eliminates the massive overheads that apache suffers.
As mentioned into previous post, I only dealt with Apache and Nginx, I have ZERO knowledge on LiteSpeed.Apache needs to check EVERY directory in the requested path for the existence of a .htaccess file and if it exists, it reads EVERY one of them and parses it. This happens for EVERY request.
I was referring to the way Apache works, not LiteSpeed:
As mentioned into previous post, I only dealt with Apache and Nginx, I have ZERO knowledge on LiteSpeed.
It is nice that LiteSpeed does not follow the Apache footprint for .htaccess.
You should stop using .htaccess period, is horrible for performance.
I see, thanks for explaining.I was refering to this comment...
I see, thanks for explaining.
The good part about LiteSpeed .htaccess that the data is cached, but I think it still behaves like Apache... except that it looks into memory for .htaccess data? Which is a lot faster. To my understanding, .htaccess files need to be scanned constantly, regardless if they are cached or not. To myself, this is still an overhead... even if cached. Why not simply avoid it, like is done in Nginx?
location /go {
...
location /go/openssl {
return 301 https://www.axivo.com/community/threads/180/;
}
...
}
We use essential cookies to make this site work, and optional cookies to enhance your experience.