A poorly optimized query or a query that returns too many results (too many as un hundrends of thousands), but it doesn't make sense to execute a query that large in a request / response cycle.
Or too many subsequent queries after the original one Without more information it's kinda hard to tell On 1/4/17, [email protected] <[email protected]> wrote: > In local host, for a particular query data(which is very huge) is coming up > > but for the same query in apache it is taking too much of time like 1 hr or > > more. I tried using caching of a page , even for that also Django works per > > user request ie for the first time for every user it will take much time > and from the second time onwards cached page will comeup with no time. > Can anyone tell me what will be the root cause of it. > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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/151cacab-ef29-4439-9f5b-90b130555ccc%40googlegroups.com. > 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 [email protected]. To post to this group, send email to [email protected]. 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/CALn3ei0M3fOQCi%3DLq6wS5hX7f0CvL%3DwQOnjjtj0HDiPeZM4wQQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
