#36526: bulk_update uses more memory than expected
-------------------------------------+-------------------------------------
Reporter: Anže Pečar | Owner: Jason
Type: | Hall
Cleanup/optimization | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* resolution: => duplicate
* status: assigned => closed
* type: Uncategorized => Cleanup/optimization
Comment:
Thank you Anže Pečar for taking the time to create this report, and thank
you Jason Hall for your interest in fixing this.
Simon, I agree with you this report is a dupe of #31202, but I also wonder
if we should consider a similar note to the one added in #28231 for
`bulk_create` and more efficient batching?
--
Ticket URL: <https://code.djangoproject.com/ticket/36526#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198513eef3a-06ad2946-1397-40c4-bb08-f3a495a9503f-000000%40eu-central-1.amazonses.com.
