angular-ui/ui-grid

excessColumns causes a performance bottleneck

Open

#5,288 opened on Apr 6, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (5,395 stars) (2,496 forks)batch import
help wantedseverity: performance

Description

Hi, As virtulization causes to show white spaces when it is scrolled horizontally, used the following gridOptions excessColumns: 150,virtualizationThreshold: 15, to render all 110 columns. Since, it renders all the columns during initial time, it increases the initial rendering time. Is there a way where we can render partially during the initial time and the remaining grid in an asynchrenous call? is it possible with current version? Please help us. This is performance bottleneck.

Contributor guide

Tech stack
javascriptangular
Domain
frontend
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
unclear
Prerequisites
Angularui gridperformance profiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the virtual scrolling and rendering implementation in ui grid to understand how excessColumns and virtualizationThreshold interact. Look for opportunities to implement partial rendering with asynchronous loading, possibly by modifying the grid's rendering pipeline.