That's the thing. When I remove all functionality of my app and simply create
a new one whose only function is to return a json object of {"test":"memory"} I
see this behavior. I was thinking that perhaps the memory was climbing because
I was importing a module at the wrong place or something.
I'm going to go back and try to recreate this from a completely fresh web2py
install, just in case Ive changed something that I don't remember. I'll let
you know what I find. It's such a fantastic system, whatever I can do to help
track it down so others don't bump into it somehow in the future.
On Feb 10, 2013, at 8:22 PM, Massimo Di Pierro wrote:
> 2 requests/second seem slow. What does your app do? Look at
> {{=response.toolbar()}} and see which DB query and how long they individually
> take.
--
---
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/groups/opt_out.
