Hi Jonathan, Thanks for the information. It really helps.
We would certainly look into nginx. Could you please suggest if embedding Python applications (including Pylons/Pyramid) in the Web Server (like nginx) would be the best approach (if it is possible to do so with nginx)? Or redirecting the traffic from the web server (like nginx) to the WSGI server (With Pylons/Pyramid application) would be a good approach? We would be looking at this from the performance point of view. I think Interprocess communication sometimes creates an overhead unless we have a distributed system spawning across multiple servers - wherein we can have load distribution across multiple instances. Something like the web server (nginx) distributing the load across multiple instances of the WSGI servers (if it is possible to do so) - without obviously creating a bottleneck at the web server and the web server is just a simple process routing traffic between the WSGI servers/application and the network. Looking forward to your thoughts... Thanks, Pinakee FE- Mail: [email protected] I IWeb: http://www.vvidiacom.com Please don't print this e-mail unless you really need to, this will preserve trees on planet earth. ----------------------------Disclaimer------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The information contained in this message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and permanently delete this message and any attachments from your system. Please note that e-mails are susceptible to change and malwares. VVIDIA COMMUNICATIONS PVT LTD. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. -------------------------------------------------------------------------------------------------------------------------Disclaimer---------------------------------------------------------------------------------------------------------- -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Vanasco Sent: 08 June 2012 01:57 To: pylons-discuss Subject: Re: Pylons/Pyramid Performance YouTube and many other major properties adopted Lighttpd around 2005-2008. It was the first high performance lightweight server , with documentation in English. It also had a lot of memory leaks and other bugs. But it had high performance and you could just have a cron-job kill&respawn it hourly. Nginx, at that time, was just as robust and had no major issues -- except the docs were entirely in Russian and the mailing list / community was mostly in broken English. Over time, the Nginx community came up with English docs & a great wiki. Many of the Lighttpd users were frustrated and dropped lighttpd for nginx or Apache2. Quoting nginx.com ( http://www.nginx.com/company.html ) """ It is used by 10.15% of all web sites and over 25% of the top 1,000 busiest web sites on the Internet, including Facebook, Zappos, Groupon, LivingSocial, Hulu, TechCrunch, Dropbox and WordPress.""" lighttpd isn't even on those charts. No one publicly knows what YouTube is using for videos today. Their main site is in Apache, and their videos have a cryptic "gvs 1.0" header, which could stand for "google video server" or the name of the CDN application. Whatever the cause, I strongly doubt that Lighttpd is still in use. The site has been barely updated over the past 5 years ( the benchmarks are even 5years old) Also worth nothing that the front page of lighttpd.net claims YouTube , WikiPedia and Meebo -- however meebo shows nginx, WikiPedia shows apache on html and "Sun-Java-System-Web-Server/7.0" on assets. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
