> sometimes going beyond 100% how??
You can use django-debug-toolbar on your development machine, check the logs for the pages that take the longest to process and the one that are the most requested and start with those, of course your CPU won't be high but you should check and compare if there were improvements after changes. Do you know already if the CPU usage spike is caused by django and not another software? do you have other stuff in the same server? database? elasticsearch? mongodb? celery workers? were specifically are you using cache? I'm not familiar with the technical term "all over the place" > does the Django ORM increase the CPU usage? using the ORM increase the CPU usage if you compare to not using it, the fastest code is the one that does't run Avraham On Wed, Feb 24, 2016 at 9:10 AM, Asif Saifuddin <auv...@gmail.com> wrote: > What is your server configuration and system usage statistics? > > On Wednesday, February 24, 2016 at 10:59:28 AM UTC+6, Web Architect wrote: >> >> 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+unsubscr...@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/69176a56-5604-4b3e-9887-9ebedf55dbb4%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/69176a56-5604-4b3e-9887-9ebedf55dbb4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/CAFWa6tJtGdFCfxbv8uXyz-NE4NUwx_PTA3ZSqBcSwtZgAD1epw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
