Barring him sharing that information, what general advice can you give regarding this?
For example, should you store sessions in redis and setup squid and nginx on the hosts? How do you handle the migrations, etc? On Saturday, April 18, 2015 at 8:26:00 PM UTC-7, Massimo Di Pierro wrote: > > For use to help you we need more info about the architecture. There two > ways you can do this. > 1) you can share information on this list and we will all help and > everybody will learn. 2) you can ask for private consulting from one of the > companies that provide web2py support. If you need advice, please contact > me personally. > > Anyway. Web2py is designed to scale horizontally by adding server behind a > load balancer. You can increase the number of requests per machine by > improving caching. Eventually you hit the database bottleneck. That is a > framework independent problem. If that is the problem you want to look into > optimizing queries. Some times it can be done and some times it cannot. > Some times you have to move to a NoSQL database like Google Cloud Storage > or Mongo. > > Massimo > > On Saturday, 18 April 2015 19:04:54 UTC-5, Sandeep wrote: >> >> We run major application in India with over 1 million users, and >> relatively high concurrent users traffic, which spikes twice a day. >> Recently we are experiencing a lot of troubles in scaling. We would love to >> get opinion from any consultant who provides support for web2py application >> in India. Any help in this regard would be appreciated. >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
