Definitely echoing Scott's sentiment here. Start with what changed. In my personal experience, if the answer is "nothing," you can narrow it down very quickly. Start by reloading with the browser network monitor in the foreground. If the first response comes back very quickly, Django itself is off the hook and you proceed with front-end optimizations. If it doesn't, and you're really sure that no one changed anything (check top or the process manager to make sure there's nothing new running!), it's your database. You need your data set to be shrunk, indices to be improved, or queries to be optimized. Django Debug Toolbar will help you see which of these apply to you. If you see hundreds of queries where you expected just one or two, look for any model reference in a loop, including template code.
If you'd like extra reassurance that that's the problem, point your config to an empty database, run the migrations, and see the difference. On Fri, May 3, 2019 at 10:59 AM Scott Miesbauer <scottmiesba...@gmail.com> wrote: > I apologize if I missed it but did someone find out what started happening > in Feb that might have some impact on the performance lag? > > The very first thing I ask when troubleshooting is “What changed?” > > So what changed in your environment in February? Other teams changes? > Application? Network? > > If you find what changed then the solution might end up being right there > in front of you. > > Good luck! > > Sent from my iPhone > > On May 3, 2019, at 1:26 AM, Saurabh Adhikary <adhikarysaur...@gmail.com> > wrote: > > Hello Uri, > > The project I handle is quite big , so before taking it up as a major > task, I wish to get it from the experts that is the django version the > issue or python version or am I missing out on something major. > > The issue started to escalate from Feb '19 , after which even a new > powerful server could'nt give us good performance. > *Now after adding extra indexes , at least the website is loading.* > > We are still not sure if we can handle around 5K - 10K concurrent request > with a 128GB SSD server. > > On Thursday, 2 May 2019 18:11:05 UTC+5:30, Uri Even-Chen wrote: >> >> Why don't you upgrade Django at least to 1.11? Django 1.8 extended >> support ended last year. >> >> https://www.djangoproject.com/download/ >> אורי >> u...@speedy.net >> >> >> On Thu, May 2, 2019 at 2:39 PM Saurabh Adhikary <adhikar...@gmail.com> >> wrote: >> >>> Hello , >>> >>> I'm using Django version 1.8.1 and Python version 2.7.12 . Suddenly >>> since Feb '19 there has been a drastic decrease in my website's response >>> rate. >>> For sure , there has been some minor increase in the no of hits, but the >>> performance is too bad. >>> >>> Initially , the thought came that the hardware of the server was old , >>> so a new server with high configuration was bought. >>> We have done the new indexing also on it. >>> Still the sought for a higher performance is awaited. >>> >>> >>> Is it that the Django support for 1.8.1 or Python support for 2.7.12 has >>> reduced and that is casing the website to slow down or I am missing out on >>> something ? >>> Kindly help. >>> >>> -- >>> 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...@googlegroups.com. >>> To post to this group, send email to django...@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/238a6da2-8f34-4b8b-939c-e20d4306545b%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-users/238a6da2-8f34-4b8b-939c-e20d4306545b%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/08bc1409-322e-41ce-a94b-5dd9db888e86%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/08bc1409-322e-41ce-a94b-5dd9db888e86%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/05C52FE4-C1E8-45F1-8146-A9C6D3154AC2%40gmail.com > <https://groups.google.com/d/msgid/django-users/05C52FE4-C1E8-45F1-8146-A9C6D3154AC2%40gmail.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/CA%2Bv0ZYWFB8O1Cc5ahuXjDjweZxZ0FDSoJVShYjoCycBUs_wu%2BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
