MSAMM
Back to course

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

Lab briefing · Ten times the data

Lesson 155 of 176 · 2 min

Run a working screen against TEN TIMES THE ROWS, find THE FIRST THING THAT BREAKS, and fix it BY DESIGN RATHER THAN BY CONFIGURATION. The lab is volume rather than profiling, because Lesson 7 established that the defects are not subtle — they are absent at the size everybody builds against. TAKE A SCREEN THAT WORKS AND MEASURE IT FIRST, AT ITS CURRENT SIZE. Request count, total transferred, time to something usable. Lesson 1's baseline, and without it you cannot say what got worse. THEN GET TEN TIMES THE ROWS AND MEASURE AGAIN. The interesting figure is not the new number — it is how the numbers SCALED. A response that grew ten times is over-fetching; a REQUEST COUNT that grew ten times is a call per row, and those are completely different diagnoses. THAT SCALING RATIO IS THE POINT OF THE LAB. It tells you which of Lessons 2,

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