#31202: Bulk update suffers from poor performance with large numbers of models
and
columns
-------------------------------------+-------------------------------------
Reporter: Tom Forbes | Owner: Tom
Type: | Forbes
Cleanup/optimization | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mikuláš Poul):
I was running some more experiments earlier, just now got to analysing
them: it doesn't seem like it depends on the type of field, at least in
the couple of types I have in my project specifically (see
https://github.com/mikicz/bulk-update-
tests/blob/master/single_field_comparison.pdf). The performance is linear,
in both number of objects to be updated and number of fields to be updated
(see https://github.com/mikicz/bulk-update-
tests/blob/master/two_fields_comparison.pdf and https://github.com/mikicz
/bulk-update-tests/blob/master/all_fields_comparison.pdf).
The code that was running the experiment is in the `experiment` app.
--
Ticket URL: <https://code.djangoproject.com/ticket/31202#comment:4>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.137936df24bc769a1d8cd826eac3f23f%40djangoproject.com.
