#28518: improve performance of loading geometries from DB
-------------------------------------+-------------------------------------
Reporter: Sergey Fedoseev | Owner: Sergey
Type: | Fedoseev
Cleanup/optimization | Status: closed
Component: GIS | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sergey Fedoseev):
[https://github.com/django/django/pull/9329 PR]
Before:
{{{
In [2]: %timeit for x in City.objects.all()[:1000]: pass
106 ms ± 802 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
}}}
After:
{{{
In [2]: %timeit for x in City.objects.all()[:1000]: pass
81.8 ms ± 595 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28518#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 [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.4fa06672e50c10c8ccfa1b82c1ab92f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
