Hi!
I have seen such a behavior on a couple of sites running an older version of Zinnia. It simply hit the 100% CPU usage on some queries.
I would also suggest integrating New Relic. It gives you a pretty detailed information on where the CPU is spending most of the time.
miercuri, 24 februarie 2016, 06:59:28 UTC+2, Web Architect a scris:
-- I have seen such a behavior on a couple of sites running an older version of Zinnia. It simply hit the 100% CPU usage on some queries.
I would also suggest integrating New Relic. It gives you a pretty detailed information on where the CPU is spending most of the time.
miercuri, 24 februarie 2016, 06:59:28 UTC+2, Web Architect a scris:
Hi,We have an ecommerce platform based on Django. We are using uwsgi to run the app. The issue the CPU usage is hitting the roof (sometimes going beyond 100%) for some scenarios. I would like to debug the platform on Production to see where the CPU consumption is happening. We have used Cache all over the place (including templates) as well - hence, the DB queries would be quite limited.I would refrain from using Django-debug toolbar as it slows down the platform further, increases the CPU usage and also need to turn the DEBUG on. Is there any other tool or way to debug the platform? Would appreciate any recommendations/suggestions.Also, does the Django ORM increase the CPU usage? Does it block the CPU? Would appreciate if anyone could throw some light on this.Thanks.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/13d4f568-2b1c-44a4-90c1-219a21bb66c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment