The OP, Lorin, asked "What's the 'largest' scale web2py is known to perform well on? "
Massimo evaded the question and no one else has provided an answer. Hence the elephant in the room has been ignored. Web2py is designed to use an OS 'thread per web' request as Web2py is built on a WGSI infrastructure. 'Thread per request' web serving is an approach that has been conclusively proven to scale very badly compared to using events or message queues (such as Erlang). Even when Web2py does not get its request through a thread, Web2py forces requests into a thread in order to use the WGSI infrastructure, such as requests passed through a single UNIX socket from Lightttpd. As an aside, the core of Erlang is very simple. Erlang uses message queues to simulate multiple processing. That is it. This is different from using events because each so called 'process' in Erlang pumps or 'processes' its own message queue in its own time. In fact Ericsson, the original sponsor of Erlang, at one stage dropped using Erlang in favour of porting the Erlang approach to other languages. There are other web2py 'elephants in the room', such as the dependence and direction of web2py on the enormous talents of a single individual: Massimo. As an example of just how big an issue this is, The Linux Foundation compiles surveys that points out just how minor the role of Linus Torvaldis is in both writing kernel code and and in committing code and also just how much code comes from corporations as opposed to what might be called lone geeks (called consultants in surveys). I think Linus has even dropped out of the top 30 individual contributors for writing kernel code. The message is very clear. If Linus suddenly decides he has had enough or wants to wind down, 'offcial' Linux continues on. A professional approach requires hard fact and a serious approach to legitimate issues that at the very least acknowledges legitimate issues and avoids propaganda. Hard facts requires real world tests, not evasion, defensive speculation and evangelism. John Heenan On Dec 2, 5:09 am, Branko Vukelic <[email protected]> wrote: > Erlang is for humongous, real-time, distributed, and highly-available apps. > Here's an example (maybe quoted one time too often): > http://www.sics.se/~joe/apachevsyaws.html > On Wed, Dec 1, 2010 at 6:45 PM, John Heenan <[email protected]> wrote: > > The elephant in the room has not gone away Massimo. > > Web2py is great for small projects. > > DotNet is great for small and large projects. > > The elephant in the room is not only the untested scalibility of > > web2py but also the amount of resources that neeeds to be thrown at > > web2py compared to DotNet and other frameworks as scale increases. > > One of the glaring defciences in web frameworks that use Python is the > > glaring engineering weakness of using thread per request web serving > > instead of using event per request web serving. I think I have pointed > > this out a number of times on this fourm, but it just does not sink > > in. I even pointed out how Linux loast a PR war over this issue. > > There is no need for Python based web frameworks to use thread per > > request web serving. > > John Heenan > > On Nov 30, 4:05 am, mdipierro <[email protected]> wrote: > >> You achieve scalability by replicating the web server behind a load > >> balancer. This is documented in the book, chapter 11, using HAProxy. > >> All frameworks work the same way in this respect. web2py has no > >> intrinsic limitations. The bottle neck is the database connection. All > >> frameworks have the same problem. You can replicate the database too > >> and web2py supports multiple database clients with Round-Robin. > >> On a small VPS, web2py in average, should execute one page in 20ms. > >> Depending on how many requests/second you need you can determine how > >> many servers you need. > >> web2py apps run on Google App Engine and that means arbitrary > >> scalability as long as you can live with the constraints imposed by > >> the Google datastore (these limitations will go away as soon as Google > >> releases MySQL in the cloud, which they announced some time ago). > >> Please ask the consultant: which .NET feature makes it scale any > >> better than web2py or Rails? If he explains we can address it more > >> specifically. > >> Massimo > >> On Nov 29, 11:56 am, Lorin Rivers <[email protected]> wrote: > >> > The project I'm working on has hired a consultant who is now > >> > recommending .Net in place of web2py or even rails. > >> > What's the 'largest' scale web2py is known to perform well on? > >> > -- > >> > Lorin Rivers > >> > Mosasaur: Killer Technical Marketing <http://www.mosasaur.com> > >> > <mailto:[email protected]> > >> > 512/203.3198 (m)
