also would be helpful if you could give some examples. All that is stated
is "there's a significant slowdown", but nothing where or if there's been
any tracing in place.
Is this happening with db queries?
serializing?
rendering?
are you using old packages which might have open/closed
Hi! And thanks for the reply!
I've read the release notes but couldn't see anything that popped out as
the possible cause. But I'm going to give them another read. Currently, the
app is running fine on 3.0, and I haven't started debugging what might be
the cause. I started with a message to
Hi! This is a very interesting problem, and I'm afraid I'm not qualified to
answer it. What I'd like to point out is that, if I had done all the work that
you seem to have done, I would be tempted to start bisecting in between versions
3 and 3.1 in order to find the exact commit that causes the
Hi!
I've recently upgraded an old Django app from Django 1.11 all the way up to
Django 4.0. Even though the app is pretty large, the migration went smooth
(or so I thought). However, when all tests passed and I deployed the app to
production, I saw that the response time of the app took a
4 matches
Mail list logo
