if you have a function that launches an external process and it takes 2.55 seconds, it will take the same when launched via the scheduler. The scheduler adds up the time it takes to create the web2py env (usually far less than half a second) in which the function is executed, but your "external process" needs to take the same amout of time in either way.
On Wednesday, October 22, 2014 5:21:43 PM UTC+2, Carolina Nogueira wrote: > > Hey guys, > > I have a performance question about the scheduler. My script is in python3 > and when I run directly on a terminal, I have a response time about 2.55s. > If I run exactly the same script inside a scheduler task with > subprocess.check_output, my response time is increased by 100 times slower > than the direct one. > I'm measuring the response time using the difference from two calls of > time.clock(), one at the beginning of the script and a second one whenever > it finishes to execute. > Does it make sense? > > I'm not quite sure whether I am doing something wrong or not... As far as > I understand, the overhead from the web service should be completely > located outside the script and not reflect during its execution. What am I > missing here? Any direction from where should I look for? > Thanks in advance! > -- 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.
