- Are there any large web2py installations that I can quote as an example Not that I know and handle >1000 requests/second.
- How are the issues of caching (say rendered pages) handled? I have done a few Drupal sites and can see the performance effects of caching very clearly. IIRC only Django has caching in the python world? If you use multiple installations behind a load balancer I suggest you use the "pound" load balancer to keep sessions sticky. In that case the different processes do not need to share any data. - Has anyone done any work with web2py in a cluster (similar to a Tomcat cluster behind mod_jk)? (multiple machines running web2py, the session data sync'd etc. I can put the session info in a shared FS though) If you need sessions and you need sessions synced, I suggest you share the sessions folder. Massimo On Jul 21, 12:20 am, Bottiger <bottig...@gmail.com> wrote: > If it is truly not computationally intensive, and does not even use a > database, it should not be a problem. > > I have benchmarked Web2Py on the static welcome page to 700 requests/ > second with a concurrency level of 50. > > To increase the level of concurrency (if you have additional CPU > cores), you should increase the number of Web2Py processes. > > "~ 8000 users, and atleast 1000-2000 simultaneous users." > > This is not really a large installation if it doesn't use a database. > > "How are the issues of caching (say rendered pages) handled? I have > done a few Drupal sites and can see the performance effects of caching > very clearly. IIRC only Django has caching in the python world?" > > Drupal, Django, and Web2Py have equivalent caching mechanisms. Any > external caching mechanism you have seen with Drupal should also be > usable with Web2Py or Django. > > "I can put the session info in a shared FS though" > > You can either do that or use a database for sessions. > > On Jul 20, 8:54 pm, Anand Vaidya <anandvaidya...@gmail.com> wrote: > > > Hi > > > After a couple of web2py projects, I am confident of coding a fairly > > big app in web2py. > > > My previous projects did not need any database (we had to use > > flatfiles), the new project is also similar. I intend to bypass the > > models etc completely. > > > The app is likely to be used in a corporate setting with ~ 8000 users, > > and atleast 1000-2000 simultaneous users. > > > The users authenticate to an LDAP server. > > > The app is not computationally intensive > > > It queries another service and displays results > > > No SQL DB is required > > > Most likely behind a few Apache 2.x front server > > > I'd like to know: > > > - Are there any large web2py installations that I can quote as an > > example > > > - How are the issues of caching (say rendered pages) handled? I have > > done a few Drupal sites and can see the performance effects of caching > > very clearly. IIRC only Django has caching in the python world? > > > - Has anyone done any work with web2py in a cluster (similar to a > > Tomcat cluster behind mod_jk)? (multiple machines running web2py, the > > session data sync'd etc. I can put the session info in a shared FS > > though) > > > Regards > > Anand --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@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 -~----------~----~----~----~------~----~------~--~---
