transaction.atomic

[devxpy]

Use transaction.atomic sparingly as it has a performance penalty. sending emails, doing any form of HTTP calls or CPU bound work is not allowed. Restrict usage to include database work ONLY.

https://docs.djangoproject.com/en/5.0/topics/db/transactions/#controlling-transactions-explicitly

Performance considerations

Open transactions have a performance cost for your database server. To minimize this overhead, keep your transactions as short as possible. This is especially important if you’re using atomic() in long-running processes, outside of Django’s request / response cycle.