To me there are three issues with scalability: - database, it is always the bottle neck but there is no differencd between web2py and rails in principle. They can use the same database architecture. - filesystem. web2py by default uses the filesystem more than rails (to store sessions for example). It needs to be configured to store everything on database or, better, to use sticky sessions - caching. You need to cache as much as you can. The built-in system is ok if you have one web2py instance and if you reuse the same keys else you can have a memory leak (keys do not expire with cache.ram). It is better to use proper caching, for example redis. Both web2py and rails work well with Redis. This should always be the last step in development anyway. - use nginx to serve static files.
Everything else should not affect scalability. On Saturday, 3 August 2013 14:18:07 UTC-5, Joe Barnhart wrote: > > I'm not the OP, but I am also risking web2py on a "large" project... > > In my case I'm replacing a Rails site that services about 15,000 customers > and has a variable workload -- about 5000 users compete for time on the > site every week. It has a database size of about 20GB of small records > (~1K ea.) and each user will require about 200-500 DB requests over the > typical session of about 30 min. The site currently does about $200k in CC > charges per month. > > I am looking at deployment on OpenShift or its brothers, or AWS. I > considered GAE but the limitations on "join" make life difficult for me as > my db is extensively indexed and cross-linked. It has about 40 tables and > they participate in a lot of 1:many joins. I'm pretty happy with > PostgreSQL as my database but I have not determined the right web server > platform for me. I'm actually a bit mystified by the choices (nginx, > apache, etc) so I'm getting a friend who knows a lot more than I to help in > that area. > > As a developer, web2py thrills me. Having lurked here a lot I'm pretty > confident it can be scaled up to handle the load, but there's always a risk > -- is my db schema flawed in some way, or other design decisions that > crater performance? The current Rails site is pretty well loved but it > bogs and people are not happy with response time. Also, my end goal is to > scale this site x10 or more, so scalability and stability are paramount! > > -- Joe B. > > P.S. I'm going to tithe a percentage of my site's profits back to web2py > development when it is up. I believe in giving back to those who help you > achieve. > > P.P.S. No, it's not a p0rn site... ;-) > > On Friday, August 2, 2013 2:46:31 PM UTC-7, Aurelio Tinio wrote: >> >> Curious to hear, what do you consider large scale? >> The more detailed you are about your project the better the response the >> community can provide. >> >> Fwiw, having only worked with web2py since the beginning of the year I've >> been contemplating similar questions too and essentially the answer is... >> *it depends*. I've predominantly worked with other web frameworks >> (mainly Django) in the past and there are definite pros/cons/tradeoffs in >> my mind of why it'd be better to choose one versus the other. Happy to >> elaborate but again, please provide more info so the reply could be more >> targeted. >> >> Cheers. >> >> On Thursday, August 1, 2013 8:04:27 PM UTC-7, hello world wrote: >>> >>> Hey >>> I would like to know if web2py framework ...is a good framework for >>> making large scale websites...???.. >>> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
