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.