-
Notifications
You must be signed in to change notification settings - Fork 13
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
Search sluggishness #67
Comments
The newer version of typeahead.js limits the number of results put into the suggestions dropdown.
Update to typeahead v0.11 to fix issue #67
did this upgrade improve performance any? I don't have IE or any sluggishness to compare to. I did find changing the minLength to 2 in $("#addressInput").typeahead({ |
It could be better, but that change did improve the results. I've experimented some with changing the input length. That is a good way to improve performance; we need to account for the properties re-appearing on the map when the field is cleared. |
After working with Jeff today, we have come to the realization that the site is perpetually searching after typing anything in the search field. I hypotise that this is because of the search index array "markerSearch" is dynamically updated. |
Good find! 👍 |
Well, we were wrong. I profiled the website. It is used to update the map according to the search result. However, when the user clicks on the search box, setMarkers takes 900ms to complete. After the initial character it takes another 400ms to complete. Following keystrokes takes less time due to diminishing results. And then, when there's no result found, setMarkers again sets all the markers and takes 900ms to complete. |
This is a issue related to leaflet dependencies. They resolved this issue (#357) with the current version. Could someone please update the following dependencies to their current versions? |
Could you try this locally to confirm that it is the problem? The |
I don't have my development environment setup yet. So, I had to improvise. I confirmed that the solution worked by manually replacing javascript references (leaflet, leaflet.markercluster and leaflet.awesome-markers) in the index.html. |
Much better... good find with the leaflet dependencies. I've pushed the change to the live LotLinker site. 👍 |
LotLinker has always had a noticable delay in accepting user input & returning search results. This is especially bad for IE, which displays the 'this page is not responding due to a long running script message'.
How can we improve the experience?
Ideally, we:
Open to:
The text was updated successfully, but these errors were encountered: