On Tue, Jan 13, 2009 at 10:10 PM, Tycon <[email protected]> wrote: > > Actually I have apache+modwsgi running flawlessly, and everything I > said is based on meticulous performance benchmarking and theoretical > profiling of deployment architectures. > > All benchmarks were performed on pylons full stack production mode, > with debugging and logging turned off. The test was a simple "hello > world" page with no template rendering, database access or other > external links or references. Apache is prefork MPM v2.2.8 with > modwsgi 1.3 using python 2.5.2. > > The benchmarks CLEARLY show that using a stand-alone app server is > MUCH faster then using apache+modwsgi to serve a page (returned from > the aforementioned "hello world" controller action). When using > CherryPy as the HTTP server for pylons, the req/sec is almost twice as > fast as apache+modwsgi. PasteHTTP is 15% slower than CherryPy but > still much faster then Apache+modwsgi. >
I'm sorry but that isn't a viable testing environment. template rendering and db access are the most time consuming tasks pylons will undertake. On the other hand you never pointed out how many request per second are you sending to the system. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
