Ok, I read the Template.py code and noticed the fact that I forgot to use
cache=True in the render statement, hence, templates are reloaded on every
visit. It is the actual reloading (which I called compiling before) what is
calling the transform.py so many times and consuming most of the cpu time,
once the cache is activated the cpu time drops drastically:
took 0.0281779766083 seconds
2826 function calls (2809 primitive calls) in 0.028 CPU seconds
Ordered by: internal time, call count
List reduced from 96 to 40 due to restriction <40>
And transform.py is no longer called. However, I noticed that the cache
seems to be cleaned every so often, if I make very close in time request to
the site the templates are not reloaded, but after a while of inactivity
they do get reloaded.
2010/6/15 Roman Yakovenko <[email protected]>
> On Jun 15, 8:25 pm, Emiliano Martinez Contreras
> <[email protected]> wrote:
> > @Anand I did what you said, which effectively is also what @Andrei said,
> > however the CPU time does not improve, look at the profiling output:
>
> Can you create a small & complete application, which will show your
> problem?
>
> --
> You received this message because you are subscribed to the Google Groups
> "web.py" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected] <webpy%[email protected]>.
> For more options, visit this group at
> http://groups.google.com/group/webpy?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/webpy?hl=en.
