the scheduler is designed also to support such cases. You can spin off whatever no. of workers you want from wherever you'd like. The only thing that needs to be reachable is the database where the scheduler tables are. you'll just have to copy your web2py folder (all the framework, plus the app(s)) in another server. If that one is just doing the "additional scheduler" role, instead of starting the webserver, you'll start the worker with web2py.py -K appname
On Friday, February 28, 2014 12:05:22 PM UTC+1, Andrey K wrote: > > Good day, > I am working on the application that requires run background scripts on > user demand. > At the moment I have implemented it as native web2py job scheduler. If the > demand will be high enough my server would not be able deliver all tasks in > reasonable time. Thus I am looking the way to destribute tasks to many > servers or to cluster. I wonder what is the best practice for such a task? > Is there a way to run web2py scheduler instances on different servers while > distributing tasks from web2py app to these sheduler instances? > Any ideas or directions to the solution would be very appreciated. Thank > you in advance. > Kind regards, Andrey > -- 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/groups/opt_out.
