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
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,
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
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,
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
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
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
>
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 -
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
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
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
11 matches
Mail list logo
