4. whatever you want, just avoid having large stdout (it's a general issue
in python that can't be easily fixed). one thing is avoiding db pressure on
the database... that means avoiding tenths of workers with thousands of
tasks . Another is queuing a single task per hour.
5. that's perfectly n
thanks all
1. got it
2. already tested it, the problem is, if put all tasks in 1 controller,
when 1 task is failed, then run queue task, another task that have status
is queued will get doubled.
3. going to wait for the cronlike feature in stable version
*another question:*
4. is it best practic
1. they get deleted because in the test app the controller showing all the
details just grabs every record in all tables. You don't need (nor want) to
clear everything every time you queue something...else it won't be a queue
:P
2. the deal is should the first task run alongside the second or th
On Tuesday, October 25, 2016 at 5:12:09 PM UTC-7, 黄祥 wrote:
>
> learn from niphlod github about web2py scheduler test, there are some
> question about it:
> 1. is it neccessary to delete all data in table scheduler_worker,
> scheduler_task, scheduler_run before queue the task?
> *e.g.*
> def cl
4 matches
Mail list logo
