Hi Vlad,
Thanks for the information and it definitely helps (also, would like to thank Andi for the statistics). I have been primarily a C/C++ system level programmer and architected and developed large Telecom systems (carrier grade) requiring great performance levels. Currently looking into Python and corresponding web frameworks for our platform. Some of the aspects of the design I have been pondering upon are also: · How do I handle the threads, configure them etc. at optimum level? Do I really need to bother about them with Pylons/Pyramid? The platform is Linux. · How is the performance of Paster Web server as compared to something like lighttpd (which is supposedly a light weight server)? If lighttpd, then I would need to embed Pylons/Pyramid there. (I have embedded Pylons with Apache but haven’t checked the performance). · Regarding DB, SQLAlchemy can be a choice for SQL based DB servers. Considering something like MongoDB, not sure how would SQLAlchemy help there. But certainly if I have my own DB access library using native APIs, probably a better performance can be achieved. If you or anyone has any thoughts on the above points, I would really appreciate. Regards, Pinakee 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 Vlad K. Sent: 06 June 2012 16:34 To: [email protected] Subject: Re: Pylons/Pyramid Performance On 06/06/2012 07:49 AM, Andi wrote: > just a benchmark, but better than nothing. found that during our > research. > <http://blog.curiasolutions.com/the-great-web-framework-shootout/> > http://blog.curiasolutions.com/the-great-web-framework-shootout/ > > andi > > (sent right out of my head) > The Curiasolutions shootout is interesting. However, even for a synthetic benchmark it is highly unbalanced. For example, it shows Pyramid yielding more rps than Bottle on Hello World. But then throws Pyramid way lower than Bottle on templated db task. If you take a look at the benchmark code, you'll notice: - both use SQLite with a local file db, which is ok - Bottle uses SQLite driver directly - Pyramid uses SQLAlchemy which incurs significant overhead You can use database drivers directly in Pyramid. You don't need sqlalchemy, or transaction extensions, they are not required by Pyramid, just a chosen default. You can also use SQLAlchemy in Bottle. You can use whatever template engine, or none, in Pyramid, and Bottle. The bottom line is Pyramid is not a full stack framework like Django, and that means you can swap out default components for whatever you want, just like you can add components to a microframework. The raw speed of a Pyramid app then really depends on the choice of components and app design. The framework overhead becomes insignificant. That said, I'd totally trust Pyramid to power my next zettascale Facebook killer. ;) -- .oO V Oo. -- 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.
