Niphlod, HUGE THANKS! I'll check that right now and post back. On Thu, Dec 5, 2013 at 11:53 PM, Niphlod <niph...@gmail.com> wrote: > check for > db = DAL(....migrate_enabled=False) > > either this prevented the creation of the table, or some another > migrate-related glitch. > To create scheduler's tables, you just need to do (as you did) > > Scheduler(db, ...) > > NB: (just a naming-convention advice) use > from gluon.scheduler import Scheduler > mysched = Scheduler(db, ....) > instead of > scheduler = Scheduler(db, ...) > > to clearly state the difference between the module and the object that is > used by your app ^_^ > > If your tables are in the admin interface but not on the backend, check that > your migrations are enabled and delete any pre-existing *scheduler*.table > files in the databases/ folder. This will trigger the creation both of the > new .table files and the tables on the backend. > > BTW: for tasks that needs **immediate** care from the scheduler, instead of > lowering the heartbeat (and such having all workers to "hammer" the database > asking for new tasks) just let the heartbeat as it is and use > mysched.queue_task(....., immediate=True) > for any user needing that task to run. > In a few sec the first available worker will pick up the task > Plan your workers number according on how many concurrent users will need in > your app a task to be processed: a worker can only be processing one single > task. > > for @all: if you have the need of 20 or 30 concurrent tasks (and such need > 20 or 30 workers ) test the scheduler carefully: you may find a dedicated > database more performant and you may also need to put workers in a sleeping > state (DISABLED) to "alleviate" the db pressure when they are not needed. > Then you'll need to set them to ACTIVE (or just delete all the records in > the scheduler_workers table) before queueing a new task...they'll resume > their (working) state in a heartbeat. > If you need more than 30 workers..... use a different task processor: > unfortunately the polling nature of the scheduler makes a "bad usecase" for > such high demands. > > -- > 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 a topic in the > Google Groups "web2py-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/web2py/qZ_RUAfqaOY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out.
-- 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.
