I agree. The bottleneck would likely be the DB, not web2py or Django or any other framework/language. Therefore, the key here is to use caching and smart db design (plus some ajax to break big DB load tasks down to smaller ones).
On Jan 1, 6:27 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > It really depends on what "Can this handle requests from 100 users > every moment?" means. > The bottleneck is probably the db. > > Before you benchmark and/or go to production make sure you: > - bytecode compile your app > - set all your models to migrate = False > > Massimo > > On Dec 31 2009, 9:00 pm, vvk <varunk.ap...@gmail.com> wrote: > > > Hi all, > > > I've to write a portal for my college in next semester. I want to > > discuss regarding scalabilty of web2py. > > > Configuration of Deployment: > > Apache + Mod WSGI + Postgresql + https only > > > Can this handle requests from 100 users every moment? > > What might be expected load on system given that machines here are of > > server class, can they handle this load, kindly suggest minimum > > configuration for this to work ? > > My application is a small one, having ten tables and conforms to 3NF, > > any suggestions here, regarding controllers or DB ? > > I'm testing my Inventory application today for scalability on a > > machine (AMD Athlon Processor 3000+, 512 MB RAM), will post results > > today. > > > ---- > > Varun -- 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.
