You can always place some more performance testing code inside your views:
import time
t = time.time()
search_time=0.00
#
#place some code which hits the database here
#
search_time+=time.time()-t
search_time="%.3f"%(search_time)
This does not test the memory footprint of your application though.
Put all your db calls into a unit test sort of framework is what i did
when developing a search engine for the site im developing.
On Thu, Dec 10, 2009 at 3:53 PM, Andy McKay <a...@clearwind.ca> wrote:
> On 09-12-09 8:43 PM, Kegan Gan wrote:
>> Thanks for reply, Andy.
>>
>> I am aware of django-debug-toolbar. I am looking something to run with
>> production.
>>
>> How do people monitor Django application performance in production
>> environment today?
>
> Hmm I guess if I knew what you were looking for I could help more. Like
> I say I've run a sql query recording tool, its v. simple. But most of
> the time I rely on system tools like munin or monit.
> --
> Andy McKay, @clearwind
> Training: http://clearwind.ca/training/
> Whistler conference: http://clearwind.ca/djangoski/
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
