Re: [I] Optimize controller UI for large cluster/tables [pinot]

["jadami10 (via GitHub)" <gi...@apache.org>]

jadami10 commented on issue #10504:
URL: https://github.com/apache/pinot/issues/10504#issuecomment-1852457305

   I'm hoping to take a pass at this during the EOY slowdown. My approach is going to be:
   - decouple rendering from data loading
   - use loading skeletons while loading data
   
   I'm going to tackle the biggest known issues first:
   - /size: this reaches out to servers for table size. and depending on current load, it can take ~forever. It also only populates numbers in the UI, so there's no reason to stop rendering the whole page
   - idealstate/externalview: this is known to be slow for large tables. It also causes memory issues in the browser tab, but i don't have an easy solution for that yet until things like the segment list do server side pagination. But this endpoint is mainly used to show the "status" of the table or the segments. Again, no need to block the whole UI from loading.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org