#27624: Optimize ORM by using more immutable data structures
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Adam
Type: | Johnson
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 1.10
(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 Keryn Knight):
* cc: Keryn Knight (added)
Comment:
Can I ask that we consider not closing it? I've only just been made aware
of this ticket (... Trac search being what it is), and it turns out it
discusses hoisting immutables to class level attributes for an
improvement, which is a branch I have recently been working on, with the
intent to fully bench (well, y'know, at least timeit/cprofile) each part
and subsequently submit a ticket/PR for discussion. If I can get around to
rebasing and re-testing, that change could potentially still land as part
of this ticket, some time after 4.0.
--
Ticket URL: <https://code.djangoproject.com/ticket/27624#comment:11>
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/068.0d8ba9beecd8c8a774baa8cee149af8b%40djangoproject.com.
