-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow search #13
Comments
We have an EATS instance containing towns and counties from the National Archives. Derbyshire has around 400 'county_for' relationships that point to the towns that it encompasses. Searching for 'Derby' takes a long time ... selecting Derbyshire to edit, it takes around 60 seconds to bring up the Edit screen. |
Sounds like there's a real need for maintaining shortcuts of the relationships in the database for fast querying, in the same way as there is for names (the NameCache model). This would be a fairly straightforward piece of work for someone to learn how the internals of EATS works. |
Happy to do it, but might need some guidance. On 5 Nov 2012, at 20:07, "Jamie Norrish" <[email protected]mailto:[email protected]> wrote: Sounds like there's a real need for maintaining shortcuts of the relationships in the database for fast querying, in the same way as there is for names (the NameCache model). This would be a fairly straightforward piece of work for someone to learn how the internals of EATS works. — |
Did the commits in November 2012 fix this issue for you? |
The November 2012 commits did make a difference, although the search (and Thanks Phil On Sat, Jan 19, 2013 at 3:49 AM, Jamie Norrish [email protected]:
|
I've just added a little more internal caching; I doubt it will have a significant effect on your queries, but hopefully every little helps. |
I have had very good results using django-cache-manager (https://github.com/vijaykatam/django-cache-manager), such that it will be used automatically if it is listed in INSTALLED_APPS. I'd appreciate any feedback about whether this helps in other installations. |
The EATS search becomes very slow when searching for entities that have multiple relationships.
The text was updated successfully, but these errors were encountered: