#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
From looking at the profiles the performance boost is likely due to the
fact Django uses `Case`, `When`, and `Value` expressions that needs to be
resolved [https://github.com/aykut/django-bulk-
update/blob/399e64d820133a79f910682c1cf247938c5c4784/django_bulk_update/helper.py
instead of raw SQL like the third party package does].
I suspect using `RawSQL` with `CASE`/`WHEN` SQL templates instead of
`Case`/`When` expressions would significantly speed up the current
implementation.
--
Ticket URL: <https://code.djangoproject.com/ticket/31202#comment:3>
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.407eb336ecaf1e0a3791b3fe6d9d62ef%40djangoproject.com.
