Esri / Esri/bayview

Search can be slow

Open
#29 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

The search can be very slow and I think its a result of the way it automatically kicks off the search. If it starts searching and you update the search string it re-queries the services but a slow typer might then start the query process several times. The more times it restarts the queries the longer it takes overall to finish it seems though I'm just using the timestamps in Firefox's dev console to test that. Bumping the searchDelay in the search config up to 2000ms from 400ms so it waits longer to query after you stop typing seems to mitigate it but I am not sure how to properly benchmark it.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the search config and the code that automatically starts service queries when the search string changes. Use Firefox's dev console timestamps to benchmark slow typing and repeated requests, then confirm that the completed search avoids unnecessary overlapping work without losing results.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.