#27624: Optimize ORM by using more immutable data structures
-------------------------------------+-------------------------------------
Reporter: Adam Chainz | Owner: Adam
Type: | Chainz
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
-------------------------------------+-------------------------------------
Comment (by Pamela McANulty):
This was a PR comment I made that I'm duplicating here:
Given that performance optimizations often unexpectedly fail to improve
performance, and especially given the unintuitive timings on
`tuple([comprehension])` v `tuple(generator comprehension)`, I think this
PR _must_ have some before and after overall performance comparison before
being accepted and merged.
--
Ticket URL: <https://code.djangoproject.com/ticket/27624#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.7f30598c700411212e7da4231e97ea2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
