there was an issue on more than 1kb that showed pretty much a limit on python's implementation, that's solved in recent releases of the scheduler but I wonder if the "tax" on that sem_wait() is trying to flush off or read the buffered output of the task.
On Friday, November 4, 2016 at 11:50:14 PM UTC+1, Erwn Ltmann wrote: > > On Friday, November 4, 2016 at 10:44:31 PM UTC+1, Niphlod wrote: >> >> BTW: do your task write a lot on stdout/stderr and/or return huge results >> ? >> > > Probably. I wrote into the log more than usual. :( Mostly DEBUGs - it's > possible to switch off them. > -- 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.
