Separate names with a comma.
Discussion in 'Nginx and PHP-FPM news & discussions' started by eva2000, Feb 17, 2017.
Nginx keeps growing and growing NGINX moves towards web server dominance with European expansion
Pfft... htaccess files are all the rage.
LOL .. if Nginx added .htaccess support, adoption rates would go through the roof !
That would never happen.
Igor Sysoev hates htaccess. I remember reading some good one liners he said about those files a long time ago.
Indeed.. though maybe left to nginx module authors to extend nginx for such
.htaccess is a performance bottleneck. Its one of the reasons why most apache servers are slow compared to nginx.
Back in the times when i was an Apache user, the first thing i did everytime was disabling .htaccess.
Yeah it is bottleneck, but still probably one of the top reasons why folks stick to Apache over Nginx
And there's still some web apps that specifically only want to support Apache and leave Nginx configuration up to the end user i.e. Sendy.co
Oh and if LiteSpeed can achieve and even surpass Nginx's performance and still retain .htaccess and Apache mod_write compatibility, I'm sure Nginx folks are smart enough to do the same
Litespeed is faster than Nginx with .htaccess enabled?
Litespeed is as fast if not faster than Nginx at very high concurrency and request rates. This is based on my experiences working with forum and cms based sites with 500,000+ unique ip visitors per day. At the lower end concurrency and traffic, LiteSpeed and Nginx can be neck and neck. Which is why lots of folks report LiteSpeed doesn't improve on Nginx for them as they are no where near the level of high traffic environments to even notice the difference between LiteSpeed and Nginx. So since LiteSpeed is a paid commercial server, folks choose Nginx. But that changed when LiteSpeed released free open source version, OpenLiteSpeed which has same performance just no cpanel/WHM plugin support and no on the fly .htaccess file support instead opting to support Apache mod_write via admin console vhost - similar to Apache moving .htaccess rules into httpd.conf. On the fly .htaccess file and cpanel/WHM was reserved for commercial LiteSpeed web server.
It's why Centmin Mod has plans to integrate both LiteSpeed/OpenLiteSpeed (open source version) eventually to take advantage of .htaccess support as well as more performant LSAPI PHP > PHP-FPM. LSAPI PHP handler scales much higher than PHP-FPM for PHP performance too especially for non-cached PHP requests Centmin Mod will in future allow users to switch between Nginx, OpenLiteSpeed/LiteSpeed, and Apache 2.4 Event MPM based configs So Centmin Mod will be the only web stack you'll ever need - in the future
FYI, also plans to support h2o and caddy web servers but both aren't performing or scaling anywhere near LiteSpeed/OpenLiteSpeed and Nginx
I ran litespeed for a while. In fact I ran it for ruby needs before nginx was a thing and way before passenger existed. It's a shame they didn't get more attention in those formative rails years, they were a long way ahead of other solutions and it saved my day over apache.
It was when I migrated away from a dedicated server to linode vps in a emergency migration. I was struggling to get apache under control, so reached out to litespeed. Simple as out of the bo it brought apache compatibility and a fairly easy configuration. This was great as only a few days later I was flying out of the country to turkey for a climbing holiday.
Litespeed then was fine for a long time, it just kept going, I was paying for it, but no way did I need the enterprise lic. Eventually they releases openlitespeed, but I was already on nginx elsewhere. Despite initially welcoming the web ui, after a while I hated it. To nested, to convoluted and occasionally breaking the underlying xml config file.
One fine day I had a web api; top 10 uk travel site, it was in dire need of a performance boost. I found a 1 paragraph post about nginx talking to memcache. I can put ruby response data into memcache, I can get it out from nginx... brilliant stuff, now the slow ruby only has to be touched once per flush . Cool, unlike the 90k line .htaccess I found when I took over the project...
The one big plus I took from a flick through caddy docs, was it's ssl management. That is a simple setup, fire and almost forget. For a small site with a few hundred thousand visitors that's still ample performance and one less headache. The other was it's local/environment deployment story.
It's nginx's market to loose now, like it was apache's in 2004 when nginx was an upstart C10k raver.
For me, my stack in 2017 is nginx or HA up front. Then depending on what I'm excited about, it will be cowboy; perfectly capable on it's own, or puma for ruby singalongs. PHP stuff, I leave in your capable hands via this project
Interesting share @Colin
yeah the xml config file is what I have to look at for LiteSpeed/OpenLiteSpeed integration so that Centmin Mod can bypass the admin console web gui to do the same stuff via SSH i.e. creating LiteSpeed vhosts etc.
Indeed it is. Though I am waiting on Nginx to add HTTP/2 server push support !
That's not going to happen in the short term. Unfortunately.