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 
<[email protected]> 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 
<[email protected]>:

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

Reply via email to