MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 15 · Performance

Rendering a large list

Lesson 151 of 176 · 3 min

What the browser does with TWO THOUSAND ROWS, and THE COMPONENTS THAT HANDLE IT FOR YOU IF YOU LET THEM. This is the slowness that is not the network. The data arrived quickly and the page still takes seconds, because the browser is being asked to build something enormous. EACH ROW IS REAL ELEMENTS IN THE DOCUMENT, AND EIGHT COLUMNS OF TWO THOUSAND ROWS IS SIXTEEN THOUSAND CELLS. The browser lays out all of it, holds all of it, and re-does the work whenever something changes. Which is why a large list is slow to appear AND slow to interact with afterwards. AND THE COMPONENTS ALREADY SOLVE THIS IF YOU USE THEM AS INTENDED. A data grid can render only what is on screen and reuse elements as the user scrolls, so two thousand rows cost about what twenty do. It is a property of the component with the right

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 15 · Performance

  1. 1Measure before you change anything
  2. 2Over-fetching: the usual cause
  3. 3Too many calls
  4. 4Rendering a large list
  5. 5What to load, and when
  6. 6Caching, and when it lies
  7. 7What breaks: three performance failures
  8. 8Lab briefing · Ten times the data