Re: Strange issue with django

[Andréas Kühne]

Hi,

Thanks,

I know that I haven't given any other specifics, the reason for this is
that it wasn't specific and it's hard to describe. I have described as much
as possible currently.

Regarding downgrading - we have tried that on everything - we have reverted
migrations, downgraded code and versions of libraries - everything.
Unfortunately we haven't been able to rule out any culprit. The reason I
asked my first question was to hear if anyone else has experienced this -
and if they have found any reason for it. Apparently this is not the case -
so we will continue searching. But thanks for the suggestions regardless :-)

Regards,

Andréas


Den lör 28 dec. 2019 kl 12:53 skrev Integr@te System <
datacentral...@gmail.com>:

> Hi Andreas,
>
> # First at all we couldn't help anymore without specified problem as your
> necessary show no more clear details.
>
> # Tools(for profiling each running functions, many metrics need), advices
> from some other to help you see out of box and show them out to our
> supports.
>
> # Plan to upgrade, include procedure, backward version recover from
> unexpected result. Libraries, dependency and so on.
>
> Example: DRF drop python2, paging, Q object, _url... many so on.
> So I wonder your hidden work or just want to survey on community for using
> these software packages.
> Thank for sharing.
>
>
> On Sat, Dec 28, 2019, 02:33 Andréas Kühne 
> wrote:
>
>> Ok - let's take this one piece at a time.
>>
>> 1. As far as we have been able to tell is that we have nested serializers
>> for certain aspects of the application - those went from loading in 3-4 s
>> to over 40 s in different places. It's hard to exactly show, however the
>> number of database requests skyrocketed as well. But our theory is
>> currently that the related models (foreign keys) are loaded strangely.
>> 2. We aren't exactly sure WHERE the bottlenecks are happening - that is
>> also why the question is wide and generic.
>> 3. We don't have any profiling tools running in production, however the
>> figures we do have are on development.
>> 4. We upgraded from the latest version of 2.2 to 3.0 in django and
>> upgraded one minor version of DRF at the same time.
>>
>> The main issue is that we got performance issues - major performance
>> issues - while upgrading. This shouldn't be possible - not in the way that
>> it happened. What worries us is if this happens again and we don't see this
>> BEFORE a production release. That was the main problem we had.
>>
>> We have now done a lot of workarounds in place where the code was slow -
>> but we would still like to understand where the problems occur so that we
>> don't get this surprise again.
>>
>> My question was more generic - because we wanted to see if anyone else
>> had experienced the same problems when upgrading.
>>
>> The strangest thing now is that even if we downgrade the database
>> (reverse migrations), downgrade the code and so on - the requests are still
>> slow - where they haven't been previously.
>>
>> Regards,
>>
>> Andréas
>>
>>
>> Den fre 27 dec. 2019 kl 10:33 skrev 'Amitesh Sahay' via Django users <
>> django-users@googlegroups.com>:
>>
>>> Also let us know the procedure that you adopted to upgrade to the new
>>> version?
>>>
>>> Regards,
>>> Amitesh
>>>
>>>
>>> On Thursday, 26 December, 2019, 10:19:31 pm IST, Jason <
>>> jjohns98...@gmail.com> wrote:
>>>
>>>
>>> Also, you haven't stated where the bottlenecks are happening.  Is it app
>>> code, internal in django, your stack, database, networking?  There's alot
>>> of variables in play for diagnosing a major slowdown, and you've provided
>>> no information about profiling/monitoring
>>>
>>> --
>>> 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 view this discussion on the web visit
>>>
>>> https://groups.google.com/d/msgid/django-users/37b9526a-756f-4ac7-835a-af49f0dada02%40googlegroups.com
>>> 
>>> .
>>>
>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/2119895222.3536368.1577439175073%40mail.yahoo.com
>>> 
>>> .
>>>
>> --
>> 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 

Re: Strange issue with django

[Integr@te System]

Hi Andreas,

# First at all we couldn't help anymore without specified problem as your
necessary show no more clear details.

# Tools(for profiling each running functions, many metrics need), advices
from some other to help you see out of box and show them out to our
supports.

# Plan to upgrade, include procedure, backward version recover from
unexpected result. Libraries, dependency and so on.

Example: DRF drop python2, paging, Q object, _url... many so on.
So I wonder your hidden work or just want to survey on community for using
these software packages.
Thank for sharing.


On Sat, Dec 28, 2019, 02:33 Andréas Kühne 
wrote:

> Ok - let's take this one piece at a time.
>
> 1. As far as we have been able to tell is that we have nested serializers
> for certain aspects of the application - those went from loading in 3-4 s
> to over 40 s in different places. It's hard to exactly show, however the
> number of database requests skyrocketed as well. But our theory is
> currently that the related models (foreign keys) are loaded strangely.
> 2. We aren't exactly sure WHERE the bottlenecks are happening - that is
> also why the question is wide and generic.
> 3. We don't have any profiling tools running in production, however the
> figures we do have are on development.
> 4. We upgraded from the latest version of 2.2 to 3.0 in django and
> upgraded one minor version of DRF at the same time.
>
> The main issue is that we got performance issues - major performance
> issues - while upgrading. This shouldn't be possible - not in the way that
> it happened. What worries us is if this happens again and we don't see this
> BEFORE a production release. That was the main problem we had.
>
> We have now done a lot of workarounds in place where the code was slow -
> but we would still like to understand where the problems occur so that we
> don't get this surprise again.
>
> My question was more generic - because we wanted to see if anyone else had
> experienced the same problems when upgrading.
>
> The strangest thing now is that even if we downgrade the database (reverse
> migrations), downgrade the code and so on - the requests are still slow -
> where they haven't been previously.
>
> Regards,
>
> Andréas
>
>
> Den fre 27 dec. 2019 kl 10:33 skrev 'Amitesh Sahay' via Django users <
> django-users@googlegroups.com>:
>
>> Also let us know the procedure that you adopted to upgrade to the new
>> version?
>>
>> Regards,
>> Amitesh
>>
>>
>> On Thursday, 26 December, 2019, 10:19:31 pm IST, Jason <
>> jjohns98...@gmail.com> wrote:
>>
>>
>> Also, you haven't stated where the bottlenecks are happening.  Is it app
>> code, internal in django, your stack, database, networking?  There's alot
>> of variables in play for diagnosing a major slowdown, and you've provided
>> no information about profiling/monitoring
>>
>> --
>> 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 view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/django-users/37b9526a-756f-4ac7-835a-af49f0dada02%40googlegroups.com
>> 
>> .
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/2119895222.3536368.1577439175073%40mail.yahoo.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAK4qSCeUAhcoqGFesXTHvWyNGfE1-HEHASwPB8Lq-PPDhh_6%3Dw%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAP5HUWomX%2BVN6hbrnEuW29GtaWZg_gXYdNnLAacQOoHLgM_C4A%40mail.gmail.com.

Re: Strange issue with django

[Andréas Kühne]

Ok - let's take this one piece at a time.

1. As far as we have been able to tell is that we have nested serializers
for certain aspects of the application - those went from loading in 3-4 s
to over 40 s in different places. It's hard to exactly show, however the
number of database requests skyrocketed as well. But our theory is
currently that the related models (foreign keys) are loaded strangely.
2. We aren't exactly sure WHERE the bottlenecks are happening - that is
also why the question is wide and generic.
3. We don't have any profiling tools running in production, however the
figures we do have are on development.
4. We upgraded from the latest version of 2.2 to 3.0 in django and upgraded
one minor version of DRF at the same time.

The main issue is that we got performance issues - major performance issues
- while upgrading. This shouldn't be possible - not in the way that it
happened. What worries us is if this happens again and we don't see this
BEFORE a production release. That was the main problem we had.

We have now done a lot of workarounds in place where the code was slow -
but we would still like to understand where the problems occur so that we
don't get this surprise again.

My question was more generic - because we wanted to see if anyone else had
experienced the same problems when upgrading.

The strangest thing now is that even if we downgrade the database (reverse
migrations), downgrade the code and so on - the requests are still slow -
where they haven't been previously.

Regards,

Andréas


Den fre 27 dec. 2019 kl 10:33 skrev 'Amitesh Sahay' via Django users <
django-users@googlegroups.com>:

> Also let us know the procedure that you adopted to upgrade to the new
> version?
>
> Regards,
> Amitesh
>
>
> On Thursday, 26 December, 2019, 10:19:31 pm IST, Jason <
> jjohns98...@gmail.com> wrote:
>
>
> Also, you haven't stated where the bottlenecks are happening.  Is it app
> code, internal in django, your stack, database, networking?  There's alot
> of variables in play for diagnosing a major slowdown, and you've provided
> no information about profiling/monitoring
>
> --
> 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 view this discussion on the web visit
>
> https://groups.google.com/d/msgid/django-users/37b9526a-756f-4ac7-835a-af49f0dada02%40googlegroups.com
> 
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/2119895222.3536368.1577439175073%40mail.yahoo.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCeUAhcoqGFesXTHvWyNGfE1-HEHASwPB8Lq-PPDhh_6%3Dw%40mail.gmail.com.

Re: Strange issue with django

['Amitesh Sahay' via Django users]

Also let us know the procedure that you adopted to upgrade to the new version?



Regards,
Amitesh
 

On Thursday, 26 December, 2019, 10:19:31 pm IST, Jason 
 wrote:  
 
 Also, you haven't stated where the bottlenecks are happening.  Is it app code, 
internal in django, your stack, database, networking?  There's alot of 
variables in play for diagnosing a major slowdown, and you've provided no 
information about profiling/monitoring

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/37b9526a-756f-4ac7-835a-af49f0dada02%40googlegroups.com.
  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2119895222.3536368.1577439175073%40mail.yahoo.com.

Re: Strange issue with django

[Jason]

Also, you haven't stated where the bottlenecks are happening.  Is it app 
code, internal in django, your stack, database, networking?  There's alot 
of variables in play for diagnosing a major slowdown, and you've provided 
no information about profiling/monitoring

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/37b9526a-756f-4ac7-835a-af49f0dada02%40googlegroups.com.

Re: Strange issue with django

[Jason]

Do you have any performance monitoring in place, with profiling add-ons, 
like new relic's x-ray trace?

That was really helpful in figuring out a bottleneck in a django service 
last year.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/385cf9db-752b-473a-b37f-c26b866f2b2a%40googlegroups.com.

Re: Strange issue with django

[Integr@te System]

Hi Andreas,

some tools to check performance in Perf tip on mail above, to inspect
deeper.


On Thu, Dec 26, 2019, 21:21 Andréas Kühne 
wrote:

> Yeah - we have gone through the release notes - and performance wise the
> environment is the same but we got an extreme performance dip - we have
> been trying to check where we have taken performance hits - but it seems to
> be random and also in places where we didn't have any issues previously
>
> We have checked the places where we are taking hits - but my main thing is
> I would like to find out WHY this has happened - because it just happened
> spontaneously
>
> Regards,
>
> Andréas
>
>
> Den tors 26 dec. 2019 kl 15:09 skrev Integr@te System <
> datacentral...@gmail.com>:
>
>> Hi Andreas,
>>
>> Let try:
>> # Perf tip
>>
>> https://gawron.sdsu.edu/compling/course_core/python_intro/intro_lecture_files/fastpython.html
>>
>> # Release note Django 3.0, DRF vs. best version
>>
>> Hope this helpful.
>>
>>
>> On Thu, Dec 26, 2019, 20:46 Andréas Kühne 
>> wrote:
>>
>>> Hi all,
>>>
>>> We have a django backend for our application - running with DRF. This
>>> has been working perfectly since November last year. Now we have upgraded
>>> to django 3.0 and also DRF to the latest version. We also added some DB
>>> indexes. After this upgrade we now have certain endpoints that went up to
>>> 25 s loading time (from about 5 s). We have reverted most of these changes
>>> and gone through our code but still can't find where this issue is.
>>>
>>> We even reverted back to django 2.2 and the previous version of DRF
>>> which gave us reasonable speed, but it still doesn't work correctly.
>>>
>>> Does anyone have any ideas what the issue might be?
>>>
>>> Regards,
>>>
>>> Andréas
>>>
>>> --
>>> 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 view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/CAK4qSCe1Nr3c41OOG2zKz3yt2z0pEE4G-629wWsRkLeHjqaNRQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAP5HUWp2gXjRCKeqB5i3EZeSdp-tJUkHpkiUQUEJETCWp05ErQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAK4qSCdbL1h1b1dqhoLQh%3DTQ127XU0cx2Kp7KbCNKJzz_nVwYA%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAP5HUWodcoS%2B1gq2cGDErL2Re0f8aUVUF9HY671HU6w6LBHwEg%40mail.gmail.com.

Re: Strange issue with django

['Amitesh Sahay' via Django users]

Could you please let us know which part of the DRF performance dipped? We can 
try to troubleshoot accordingly.
Your statements are very generic.


Regards,
Amitesh 
 

On Thursday, 26 December, 2019, 7:51:28 pm IST, Andréas Kühne 
 wrote:  
 
 Yeah - we have gone through the release notes - and performance wise the 
environment is the same but we got an extreme performance dip - we have been 
trying to check where we have taken performance hits - but it seems to be 
random and also in places where we didn't have any issues previously
We have checked the places where we are taking hits - but my main thing is I 
would like to find out WHY this has happened - because it just happened 
spontaneously

Regards,
Andréas

Den tors 26 dec. 2019 kl 15:09 skrev Integr@te System 
:

Hi Andreas,
Let try:# Perf tip 
https://gawron.sdsu.edu/compling/course_core/python_intro/intro_lecture_files/fastpython.html
# Release note Django 3.0, DRF vs. best version

Hope this helpful.


On Thu, Dec 26, 2019, 20:46 Andréas Kühne  wrote:

Hi all,
We have a django backend for our application - running with DRF. This has been 
working perfectly since November last year. Now we have upgraded to django 3.0 
and also DRF to the latest version. We also added some DB indexes. After this 
upgrade we now have certain endpoints that went up to 25 s loading time (from 
about 5 s). We have reverted most of these changes and gone through our code 
but still can't find where this issue is.
We even reverted back to django 2.2 and the previous version of DRF which gave 
us reasonable speed, but it still doesn't work correctly. 
Does anyone have any ideas what the issue might be?
Regards,
Andréas

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCe1Nr3c41OOG2zKz3yt2z0pEE4G-629wWsRkLeHjqaNRQ%40mail.gmail.com.



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAP5HUWp2gXjRCKeqB5i3EZeSdp-tJUkHpkiUQUEJETCWp05ErQ%40mail.gmail.com.



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCdbL1h1b1dqhoLQh%3DTQ127XU0cx2Kp7KbCNKJzz_nVwYA%40mail.gmail.com.
  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1339206341.3272866.1577370248968%40mail.yahoo.com.

Re: Strange issue with django

[Andréas Kühne]

Yeah - we have gone through the release notes - and performance wise the
environment is the same but we got an extreme performance dip - we have
been trying to check where we have taken performance hits - but it seems to
be random and also in places where we didn't have any issues previously

We have checked the places where we are taking hits - but my main thing is
I would like to find out WHY this has happened - because it just happened
spontaneously

Regards,

Andréas


Den tors 26 dec. 2019 kl 15:09 skrev Integr@te System <
datacentral...@gmail.com>:

> Hi Andreas,
>
> Let try:
> # Perf tip
>
> https://gawron.sdsu.edu/compling/course_core/python_intro/intro_lecture_files/fastpython.html
>
> # Release note Django 3.0, DRF vs. best version
>
> Hope this helpful.
>
>
> On Thu, Dec 26, 2019, 20:46 Andréas Kühne 
> wrote:
>
>> Hi all,
>>
>> We have a django backend for our application - running with DRF. This has
>> been working perfectly since November last year. Now we have upgraded to
>> django 3.0 and also DRF to the latest version. We also added some DB
>> indexes. After this upgrade we now have certain endpoints that went up to
>> 25 s loading time (from about 5 s). We have reverted most of these changes
>> and gone through our code but still can't find where this issue is.
>>
>> We even reverted back to django 2.2 and the previous version of DRF which
>> gave us reasonable speed, but it still doesn't work correctly.
>>
>> Does anyone have any ideas what the issue might be?
>>
>> Regards,
>>
>> Andréas
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAK4qSCe1Nr3c41OOG2zKz3yt2z0pEE4G-629wWsRkLeHjqaNRQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAP5HUWp2gXjRCKeqB5i3EZeSdp-tJUkHpkiUQUEJETCWp05ErQ%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCdbL1h1b1dqhoLQh%3DTQ127XU0cx2Kp7KbCNKJzz_nVwYA%40mail.gmail.com.

Re: Strange issue with django

[Integr@te System]

Hi Andreas,

Let try:
# Perf tip
https://gawron.sdsu.edu/compling/course_core/python_intro/intro_lecture_files/fastpython.html

# Release note Django 3.0, DRF vs. best version

Hope this helpful.


On Thu, Dec 26, 2019, 20:46 Andréas Kühne 
wrote:

> Hi all,
>
> We have a django backend for our application - running with DRF. This has
> been working perfectly since November last year. Now we have upgraded to
> django 3.0 and also DRF to the latest version. We also added some DB
> indexes. After this upgrade we now have certain endpoints that went up to
> 25 s loading time (from about 5 s). We have reverted most of these changes
> and gone through our code but still can't find where this issue is.
>
> We even reverted back to django 2.2 and the previous version of DRF which
> gave us reasonable speed, but it still doesn't work correctly.
>
> Does anyone have any ideas what the issue might be?
>
> Regards,
>
> Andréas
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAK4qSCe1Nr3c41OOG2zKz3yt2z0pEE4G-629wWsRkLeHjqaNRQ%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAP5HUWp2gXjRCKeqB5i3EZeSdp-tJUkHpkiUQUEJETCWp05ErQ%40mail.gmail.com.

Strange issue with django

[Andréas Kühne]

Hi all,

We have a django backend for our application - running with DRF. This has
been working perfectly since November last year. Now we have upgraded to
django 3.0 and also DRF to the latest version. We also added some DB
indexes. After this upgrade we now have certain endpoints that went up to
25 s loading time (from about 5 s). We have reverted most of these changes
and gone through our code but still can't find where this issue is.

We even reverted back to django 2.2 and the previous version of DRF which
gave us reasonable speed, but it still doesn't work correctly.

Does anyone have any ideas what the issue might be?

Regards,

Andréas

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCe1Nr3c41OOG2zKz3yt2z0pEE4G-629wWsRkLeHjqaNRQ%40mail.gmail.com.