Hi everyone, I’m currently experiencing some strange behavior that I can’t quite wrap my head around, so I thought I’d ask if anyone here has seen something similar. What happened: I recently upgraded one of our larger projects from Django 4.2 (Python 3.11) to Django 5.2 (Python 3.13). The upgrad…

I found out why the perfomance tanked so much. It is caused by the sentry-sdk. I don´t know why the sdk has such a big impact in django above version 5 but i will open an issue with the sentry team to look further into this.

Thanks for the update, that’s helpful to know. We’ve been planning a similar upgrade and would’ve missed the Sentry SDK angle entirely. Curious to see what the Sentry team finds, definitely keeping an eye on this.

Hello there. Can you share which sentry-sdk version is the problem related to, or link the github issue here? I have a pending dependabot PR for sentry-sdk and remembered this post from a while ago. Thanks in advance.

Hi, the problem is not related to a specific sentry-sdk version much more the django version > 5.0. We have identified that the problem lays within the evaluation of the django_admin_log queryset which is passed with every admin call and always beeing evaluated by sentry because of a repr() call. …

I had the same issue after upgrading from Django 4.2 to 5.2. With a large django_admin_log table having 35+ million rows. What I found was that the requests were hanging on the same django_admin_log query with ORDER BY "django_admin_log"."action_time" DESC LIMIT 21 Looking at the django_admin_log …

This is a good catch, i will experiment with this just for performance reasons. The actual problem with sentry is now fixed upstream in the sentry-sdk by the folks of sentry.

Just as an update to you guys, the folks from sentry found the problematic part and fixed it upstream, should be released in the next release. fix(Django): Avoid evaluating complex Django object in span.data/span.attributes maste…

I encountered the dramatic admin slowdown after upgrading to Django > 5.0, and it continues in 6.0. My project doesn’t use sentry-sdk, and adding an index for django_admin_log didn’t help. The django_admin_log table only has 51K entries. I’ll keep looking for a fix, because this is painful for adm…

[image] f-reinsch: https://github.com/getsentry/sentry-python/pull/4804 Working around this in Sentry seems like a good choice for Sentry, but not a good idea for Django. I would consider this to be broken still.

Strange behaviour for Django > 5.0 (long loading times and high Postgres CPU load, only admin)

Using Django Mystery Errors

boxed September 15, 2025, 9:34am 7

Is this the same problem as I talk about here: Safe repr for error pages ?

Seems at least similar…

Topic		Replies	Views
Performance of template rendering in Django 4.2 vs. 5 Templates & Frontend	13	826	June 19, 2025
Admin interface no longer working after server update Mystery Errors	15	239	July 3, 2024
After upgrade to 4.0 webpages very slow response Mystery Errors	11	2818	February 19, 2022
issue for upgraded to Django 5.0.3 Mystery Errors	2	583	June 12, 2024
Commands take forever to run Mystery Errors	6	175	October 8, 2025

Strange behaviour for Django > 5.0 (long loading times and high Postgres CPU load, only admin)

Related topics