Hi Mike,
Thanks for the detailed information. With so many options available, it becomes a bit confusing to conclude on a specific design J: 1. Whether to embed the Pylons/Pyramid application in a light weight web server (like nginx as suggested by Jonathan) if possible 2. Or to redirect the network HTTP traffic from the web server to the WSGI servers (pastehttpserver, cherrypy etc.)? Which one would be the best approach in terms of performance? As far as my knowledge goes, I think 2 would be good if we have distributed systems wherein the webserver distributes the load across multiple instances of the WSGI server (given that the webserver is a light weight process just routing traffic between the WSGI servers and network). Would really appreciate your suggestion regarding the above… 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 Mike Orr Sent: 07 June 2012 23:07 To: [email protected] Subject: Re: Pylons/Pyramid Performance On Wed, Jun 6, 2012 at 9:48 PM, Biswas, Pinakee < <mailto:[email protected]> [email protected]> wrote: > The platform we are building is not simple - it’s a media (mostly video) > based content management and delivery platform with multiple features. In that case the main bottleneck will be large files for playback and, if you're editing/processing videos, the multimedia aspects of those. Neither of those has much to do with the choice of framework. Of course, you won't want to deliver large files through the framework where it has to read the entire file into Python, but rather use X-SendFile or a media server or such for them. > As far as my understanding goes on Pylons/Pyramid, the requests handling and > delivery (to proper controller and action), management of threads (not sure > if this is applicable) is handled by the framework . The HTTP protocol level > transaction handling, detailed implementation of the stack etc. are handled > by the web server/framework. > The job remaining then by the application (or the application developer) is > processing the requests and building the response (which also the framework > helps in building with various libraries). The WSGI server (Waitress, CherryPy, PasteHTTPServer) manages threads. It loads an application instance into each worker thread. Pyramid comes along as part of the application. Pyramid does nothing with threads; it runs inside a thread. The only thing it has to do is be thread-safe. HTTP issues are divided between the WSGI server and application. The WSGI server converts the HTTP headers to a basic Python data structure and may modify them. The application (Pyramid, using WebOb) converts them to another Python structure and may modify them further. The application's responsibility, as you say, is to interpret a request and decide a response. -- Mike Orr < <mailto:[email protected]> [email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to <mailto:[email protected]> [email protected]. To unsubscribe from this group, send email to <mailto:[email protected]> [email protected]. For more options, visit this group at <http://groups.google.com/group/pylons-discuss?hl=en> 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.
