Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 13 · Groovy in Application Composer
Performance: the rule that runs a million times
Lesson 133 of 177 · 2 min
A query inside a row-level trigger executes ONCE PER ROW. That sentence is the entire performance lesson and it is worth memorising in that form. How it turns a two-second save into a two-minute one. The trigger looks up a related record to check something — one lookup, a few milliseconds, invisible on a single save. Now a user saves a record with two hundred lines, or a load inserts ten thousand rows: the same lookup runs two hundred or ten thousand times. Nothing about the rule changed; only the volume did. The shapes to watch for: a lookup inside a loop over a child collection; a rule that traverses a relationship to read one field; anything that counts or sums across records to make a decision. All three are natural ways to write the rule and all three scale badly. HOW TO SEE IT BEFORE A USER DOES: test…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 13 · Groovy in Application Composer
- 1Where Groovy runs, and where it does not
- 2The language subset, quickly
- 3Validation rules that help rather than annoy
- 4Triggers and the order they fire in
- 5Object functions and reuse
- 6Performance: the rule that runs a million times
- 7Debugging without a debugger
- 8What breaks: three Groovy failures
- 9Lab briefing · A rule, and its performance