Closed misli closed 6 years ago
The test failures are due to an issue with PostGIS and TravisCI. I've merged the Django 2.0 branch, so if you rebase they should pass.
I think the current Trimet feed would be a good test of the speed impact of this change. I'm not aware of a good way to measure RAM impact in Python / Django.
Method Base.export_txt doesn't work for large querysets on models, where
_sort_order[0]
doesn't contain'__'
(Route, Service, ServiceDate). It raises AssertionError (see the traceback below) when spliting large queryset. However, the problem with large querysets may be solved much easier (and even much less RAM consuming) way with.iterator()
(https://docs.djangoproject.com/en/2.0/ref/models/querysets/#iterator).