(Original
question<http://stackoverflow.com/questions/16783197/web2py-compile-slowing-down-response-times>posted
to SO, but I realized this may be a better venue)
I am trying to boost the performance of a web2py application I have running
so I turned on the profiler and noticed an item that is consistently on the
top:
54126 function calls (53838 primitive calls) in 0.565 seconds
Ordered by: internal timeList reduced from 698 to 80 due to restriction <80>
ncalls tottime percall cumtime percall filename:lineno(function)
29 0.197 0.007 0.197 0.007 {compile}
>From most of the profiles that were taking, this one item accounts for
roughly a third of the request time and is naturally something worth
looking into. Does anyone know what this {compile} step is and how to
reduce or remote its impact?
I'd like to note that this shows up on *every* request, which is counter to
my understanding that python wouldn't recompile source files if they hadn't
changed.
--
---
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/groups/opt_out.
