I disagree. I'm getting very consistent results with time.time().

With a print statement, Welcome yields 0.587778091431 second, while the 
command line execution gives 0.0202300548553 second. Again, that's 29 times 
faster.


On Friday, 14 March 2014 11:51:04 UTC-4, Leonel Câmara wrote:
>
> Time is still a bad way to measure as the web2py version process may be 
> getting preempted and not getting as much CPU time. Althoug,h I would agree 
> there seems to be something odd going on here. Possibly dead code 
> elimination. What happens with the time if you add a "print x" after the 
> "for" to both versions?
>

-- 
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.

Reply via email to