I still can't get the """viable option for my own processing purposes, not multiple users"""
if they're viable for you, they're viable for multiple users. To a limit. BTW: you can't run external processes on GAE, there's only the TaskQueue (with some limitations) As for the number of concurrent scheduler processes, of course they're limited by the hardware you'll run them onto. If you're looking to more than 50 concurrent processes, I'd say you have to leave web2py's scheduler and resort to state-of-the-art async processing (e.g., Celery) On Friday, September 18, 2015 at 9:37:26 PM UTC+2, Phillip wrote: > > My basic interpretation of your post: The scheduler shouldn't be managed > by the webserver (shouldn't be controlled by user requests) which could > basically create zombie processess and / or will drop long-running > processes. > > If you see no reason the scheduler shouldn't work for this purpose (while > preventing long-running processes from dropping (which is what I thought > the timeout feature was for)), > > > > Could there be scalability issues with too many users attempting to run > too many processes (on GAE for instance)? > > > -- 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.
