lmenezes/cerebro

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

Open

#478 创建于 2020年9月14日

在 GitHub 查看
 (9 评论) (2 反应) (0 负责人)JavaScript (5,411 star) (721 fork)batch import
enhancementhelp wanted

描述

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!

贡献者指南

技术栈
javascript
领域
frontend
议题类型
performance
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
javascriptreactelasticsearch basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
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.
REST autocomplete very slow when having a large number of indexes/aliases · lmenezes/cerebro#478 | Good First Issue