lmenezes/cerebro

REST autocomplete very slow when having a large number of indexes/aliases

Open

#478 opened on Sep 14, 2020

View on GitHub
 (9 comments) (2 reactions) (0 assignees)JavaScript (5,411 stars) (721 forks)batch import
enhancementhelp wanted

Description

Hello,

I am noticing a case where the autocomplete section of the REST page (where the index / url is entered) it is very slow when accessing a cluster with hundreds of indexes (and even more aliases). It can take several minutes to load and makes the page hard to use.

It would be nice if this were faster, or even disabling autocomplete if the number of results is too large. Thanks!

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
javascriptreactelasticsearch basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the autocomplete component used in the REST page, likely in the frontend codebase. Look into how the list of indexes/aliases is fetched and filtered, possibly adding debouncing or limiting the number of suggestions. Check for any existing performance optimizations or discussions in the issue comments.