long story short, no. You can get better "pick-up-times" (the time that elapses from when you queue the task to when it's started) with the redis version of the scheduler but in any case the worst possible scenario won't drop under "heartbeat" which is 3 seconds. Got it, would be wonderful if the scheduler was even snappier than it is but.... the current limitation just makes sense for small corner cases, which are: - need to run the task on another server than the web-serving one - need to run zillions of tasks in a hundred workers farm to offload something the webserver can't keep up
That being said, there's another, which is "need to run tasks that go beyond the 60 seconds timeout which is enforced in most webservers"... but in that case waiting 6 seconds is not that much in comparison. The thing here is : a) you're using pythonanywhere, so you're out of "worker farms" b) your tasks are super-duper-speedy (they complete well-below the usual timeout for webserver which is 60 seconds) c) you want sub-6 seconds "pick-up time".... why don't you just use a simple ajax request ? -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
