web2py and other web frameworks all deal with concurrency in the same way. They can run multiple threads and multiple processes. It works well with multiple installation behind a load balancer such as pound or haproxy. The framework is built by avoiding use of modules that are not thread safe and there is no locking mechanism.
There is a section in the book about Scalability Issues http://web2py.com/book/default/section/11/12 and it explains how to configure web2py for scalability. The real bottle neck of any web app is the database. That is true for any web framework. Depending on the the type of queries a non- relational database (nodb) can be what you need. The web2py abstraction layer works with google app engine and we are working to port it over other NoDBs. Anyway, this is sugar and not necessary to use a nodb. In fact every nodb provides Python APIs and you can use those with web2py as you would do with any of the other frameworks. On Mar 16, 9:18 pm, Śląski <yaha...@gmail.com> wrote: > Hi, > I am planning to make some big project (100 000 users, approximately > 500 request pre second - in hot time). > For performance I'm going to use no relational dbms (each request > could cost lot of instructions in relational dbms like mysql) - so i > can't use DAL. > > My question is - how web2py is working with a big traffic, is it work > concurrently? I'm consider to use web2py or Gork - Zope, > > Could you advice me please. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
