IMO this issue shouldn't continue to be kicked down the road, and a patch
should be accepted for improved performance even if it doesn't close
#15220. It's not an easy problem for third-party apps to address and when
it gets slow it gets too slow to function.
I'm providing a pull request with changes that greatly improved
performance in my testing with 20,000 items. It's still laggy but that's
to be expected, and the goal here isn't to make it smooth as butter, but
functionally useable for users.
--
Ticket URL: <https://code.djangoproject.com/ticket/26561>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_docs: => 0
* type: Uncategorized => Cleanup/optimization
* needs_tests: => 0
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/26561#comment:1>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"fb68674ea4b05280e3deb2ed23602038755092bc" fb68674e]:
{{{
#!CommitTicketReference repository=""
revision="fb68674ea4b05280e3deb2ed23602038755092bc"
Fixed #26561 -- Improved admin's JavaScript SelectBox performance on large
lists.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26561#comment:2>